The Pattern Atlas
I look for the structure beneath the visible problem.
A component issue may begin with unclear decision rights; stalled adoption may reflect migration cost, while a broken process can point to uncertain ownership. Before prescribing a solution, I map how capability, people, decisions, and feedback currently interact.
The transformation engine
Observe the system
What is happening—and where does the stated process differ from the lived one?
- Approach
- Listen across roles, review artifacts and data, map workflows, identify handoffs, and locate recurring friction.
- Outcome
- A shared current-state picture rather than competing anecdotes.
Identify the pattern
Which underlying condition is producing multiple visible symptoms?
- Approach
- Separate capability gaps from behavior, governance, capacity, architecture, migration, or measurement gaps.
- Outcome
- A small number of places where change can matter most, with the evidence and uncertainty made clear.
Make the decision legible
What are the viable options, tradeoffs, decision rights, and risks?
- Approach
- Frame alternatives, identify reversibility, expose dependencies, define ownership, and document what the evidence does and does not prove.
- Outcome
- A decision leaders and teams can understand, challenge, and revisit.
Build the intervention
What combination of platform capability and operating structure will change the system?
- Approach
- Create roadmaps, governance, patterns, documentation, release mechanics, contribution paths, and quality guardrails.
- Outcome
- A practical system—not only a recommendation.
Create the adoption path
What must be true for people to use and sustain the change?
- Approach
- Plan migration, enablement, support, communication, incentives, measurement, and feedback loops.
- Outcome
- A sequenced path from decision to durable behavior.
Learn and evolve
What is the system telling us after contact with real work?
- Approach
- Combine usage signals, support themes, quality evidence, qualitative feedback, and changing organizational context.
- Outcome
- A living roadmap and an operating model that can adapt without losing coherence.
Principles
Treat shared systems as products
They need users, outcomes, ownership, roadmaps, support, measurement, and intentional evolution.
Match process to the work
Structure should reduce ambiguity and improve decisions. When it becomes ceremony, change it.
Make tradeoffs visible
Good leadership does not eliminate constraints. It makes the consequences understandable enough to choose responsibly.
Design adoption, not just delivery
The real product includes migration, documentation, support, trust, and the ability to contribute.
Separate evidence from inference
Metrics are useful only when their definition and limits are visible. A proxy can guide a decision without pretending to prove more than it does.
Preserve human judgment
Whether the system is a component platform or an AI workflow, structure should help people make better decisions—not remove them from decisions that require context and care.