Why should process and people considerations come before technology in organizational transformation?
Answered at 6:54 in Ep.183 -Bringing Structure and Systems to Accidental CEOs · The Conference Room with Simon Lader
Why should process and people considerations come before technology in organizational transformation?
If you start with technology alone, you simply replicate your current inefficiencies with software and call it automation—but you haven't actually improved. Starting from process allows you to identify the person who knows how things actually work and where real improvements are needed, so you can introduce technology to support those refined operations rather than codify the broken ones.
Most organizations rush to implement software solutions without first examining how their work actually flows. You end up automating waste, building digital versions of broken processes, and creating more complexity than you had before.
The right sequence is deliberate: process first, people second, technology third. When you start with process, you're forced to ask hard questions about why a step exists at all. Is it necessary? Can it be simplified? Does it add value? This is where domain expertise becomes crucial.
As Val Coyne explains in the episode, the person doing the work every day—not the executive suite—often holds the answers to how operations can be refined. They understand the informal workarounds, the missing steps in documentation, and where bottlenecks really exist.
Process clarity reveals where people create value
When you map process first, you uncover who the actual experts are within your organization. A receptionist might be handling five undocumented tasks that no system captures. A warehouse supervisor knows three ways to accelerate packing that never made it into the manual. These insights only surface when you examine process before technology.
Full answer and detailsRead the whole answer, key facts and every other question from this episode
In short
If you start with technology alone, you simply replicate your current inefficiencies with software and call it automation—but you haven't actually improved.
Val Coyne · Ep.183 -Bringing Structure and Systems to Accidental CEOs · The Conference Room with Simon Lader · answer at 6:54
Key takeaways
- Starting from process allows you to identify the person who knows how things actually work and where real improvements are needed, so you can introduce technology to support those refined operations rather than codify the broken ones.
- Most organizations rush to implement software solutions without first examining how their work actually flows.
- The right sequence is deliberate: process first, people second, technology third.
- As Val Coyne explains in the episode, the person doing the work every day—not the executive suite—often holds the answers to how operations can be refined.
- When you map process first, you uncover who the actual experts are within your organization.
The full answer · about 3 min
If you start with technology alone, you simply replicate your current inefficiencies with software and call it automation—but you haven't actually improved. Starting from process allows you to identify the person who knows how things actually work and where real improvements are needed, so you can introduce technology to support those refined operations rather than codify the broken ones.
Most organizations rush to implement software solutions without first examining how their work actually flows. You end up automating waste, building digital versions of broken processes, and creating more complexity than you had before.
The right sequence is deliberate: process first, people second, technology third. When you start with process, you're forced to ask hard questions about why a step exists at all. Is it necessary? Can it be simplified? Does it add value? This is where domain expertise becomes crucial.
As Val Coyne explains in the episode, the person doing the work every day—not the executive suite—often holds the answers to how operations can be refined. They understand the informal workarounds, the missing steps in documentation, and where bottlenecks really exist.
Process clarity reveals where people create value
When you map process first, you uncover who the actual experts are within your organization. A receptionist might be handling five undocumented tasks that no system captures. A warehouse supervisor knows three ways to accelerate packing that never made it into the manual. These insights only surface when you examine process before technology.
More answers from this episode
- 5:28What is the true definition of digital transformation beyond simply implementing software?
- 10:06How should organizations assess whether their technology stack actually supports their growth stage?
- 16:48What is the responsibility framework for managing technology redundancy and software audits in growing organizations?
- 23:00What are the common challenges that accidental CEOs face when scaling their businesses?
- 26:27What first step should leadership take to support an accidental CEO or newly promoted operations manager in their transformation?