Learn
The assessment is just the beginning.
Learn more about the six activities. How patterns form. What makes an effective team. And how to leverage the making pattern in your life.
Start here
Articles
Attention is not skill
The activity you attend to most isn't the one you're best at. It's the one that feels most urgent before you've decided anything. Understanding that distinction changes how you see your work in action.
The cost of overcurrent
When your top two activities run together, the activities at the bottom of your ranking don't just get less attention. They get squeezed. What that looks like in practice.
Where it hurts isn't where it's broken
When something goes wrong in a project, the visible failure is almost never where the problem started. Problems propagate through the making pattern. Intervening at the symptom often makes things worse.
Ready for everything, building nothing
When Scoping and Provisioning run together, they form a circuit between preparing and planning that feels like diligence. The risk: solutions going entirely untouched.
Better and better at the wrong thing
When Delivery and Verification close, they create a loop that produces improving output indefinitely. The issue: a perfectly built solution that doesn't solve the problem.
Perfectly designed, never built
When Specification and Validation get stuck, purpose and form chase each other in tight iteration. While need-solution alignment improves continuously. Nothing materializes.
Scoping and Validation: the closed loop
Scoping reads the gap between need and resources. Validation reads the gap between solution and need. Together they form the only pair in the framework that can operate as a closed feedback loop. What happens when both are high.
The Delivery trap
High Delivery attention is the most legible kind. It produces output, it ships things, it moves. The trap is subtle: output without sufficient Specification or Verification isn't progress, it's velocity toward unknown destinations.
Why Provisioning is often invisible
Provisioning (building the capacity to make) rarely shows up in project plans or performance reviews. It's preparation, not production. Yet the teams that skip it reliably hit walls.
Reading your Growth Map
The Growth Map section of your report is the most actionable, and the most misread. The growth edge isn't a weakness to fix. It's a structural gap that your current pattern creates, and the entry points for closing it are specific.
Articles publish periodically. Take the assessment to get your report while you wait.
New articles, when they publish
No newsletter cadence. Just an email when something worth reading goes up.
Quick reference
| # | Activity |
|---|---|
| 1 | Scoping |
| 2 | Specification |
| 3 | Provisioning |
| 4 | Delivery |
| 5 | Verification |
| 6 | Validation |