This is a great article. What I love is that the first step is the inventory and spec, which starts with the problem and not the tech and/or solution. Since the start of the ChatGPT buzz, we have had too much of a solution looking for a problem. Glad that you have brought this back to basics.
The three-layered mental model is particularly valuable. It gives you a vocabulary for the level you're operating at and prevents scope creep. When you're designing at the workflow layer but accidentally thinking at the task layer, you end up with brittle point solutions instead of maintainable processes.
Thanks John, the guardrails checklist particularly excellent. I also appreciate how useful this framework is for whatever AI tool you might be using. 🙏
This is where the upskilling conversation gets real. Learning a few clever prompts won’t cut it anymore — the edge now lies with people who can design systems, not just poke around in them.
What’s the biggest mindset shift you’ve seen in people making the jump from user to architect?
John,
This is a great article. What I love is that the first step is the inventory and spec, which starts with the problem and not the tech and/or solution. Since the start of the ChatGPT buzz, we have had too much of a solution looking for a problem. Glad that you have brought this back to basics.
Really appreciate that. Starting with the problem keeps you honest.
The three-layered mental model is particularly valuable. It gives you a vocabulary for the level you're operating at and prevents scope creep. When you're designing at the workflow layer but accidentally thinking at the task layer, you end up with brittle point solutions instead of maintainable processes.
Exactly, mixing layers is where most breakage starts.
Thanks John, the guardrails checklist particularly excellent. I also appreciate how useful this framework is for whatever AI tool you might be using. 🙏
That was the goal... usefulness no matter the tech.
Your piece felt like sitting with someone who’s already walked the path and is gently pointing out where the footing gets sure.
Not about shortcuts, but about understanding how to move with intention.
Through the 5 Voices lens, upskilling with tools like prompts lands differently for each person:
Nurturers want clarity on how it supports people.
Guardians want a reliable process they can return to again and again.
Creatives look for space to explore and iterate.
Connectors want to see how it helps communication and shared understanding.
Pioneers look for ways it accelerates decisions.
When leaders hold all these layers, upskilling doesn’t feel like a leap — it begins to feel like a rhythm.
You’re right that intention shows up differently depending on what people care about first.
This is where the upskilling conversation gets real. Learning a few clever prompts won’t cut it anymore — the edge now lies with people who can design systems, not just poke around in them.
What’s the biggest mindset shift you’ve seen in people making the jump from user to architect?
Do you have a general recommendation for that amount of tasks within a workflow and workflows within a system? Just curious.