Work Together
Understand the work.
Build the ability to change it.
We begin with relationships and the people on the front lines. Your mission gives the work its direction.
Start with the problem. These are the skills and tools we can bring to it.
01Data & AnalyticsUnderstand what is happening.
Bring scattered records together, explore patterns, compare scenarios, and design useful experiments. Define what a measure can tell us and what still needs a conversation.
02Systems & AIConnect and improve the work.
Understand the handoffs between people and tools. Improve a recurring task, connect existing systems, or create an AI workflow with the context and review it needs.
03Growth & MarketingImprove the customer journey.
Examine where people discover you, what helps them decide, and where they encounter friction. Test a focused change and interpret the results in context.
04Finance & OperationsPlan with clearer assumptions.
Make the assumptions behind an operating plan visible. Compare costs, resources, and scenarios so the people responsible can make a more informed decision.
05Product & Interface DesignMake the system usable.
Turn complex information and workflows into interfaces people can understand. Prototype the experience, listen to its users, and improve it through actual use.
See the experience and projects behind these capabilities.
Meet MarkSeven stages, with room to listen, question, and revise. The mission stays present throughout.
01MissionAgree on what the work should serve.
Begin with your company's mission and the people it serves. What are you trying to make possible? Every proposed feature needs a clear connection to that purpose.
02DiscoveryUnderstand the people, relationships, and obstacles.
- List stakeholders, including people affected by the outcome.
- Map people, systems, information, and their relationships.
- Identify obstacles to the mission.
- Investigate possible root causes.
- Prioritize the issues together.
We distinguish real-world people and situations from the calculations used to describe them.
First principles: define the world, decompose to the root, imagine the ideal solution, and test its limits.
03PlanChoose a useful intervention and define success.
Compare possible solutions, including changes to the process or tools you already use. Agree on scope, responsibilities, the measures of success, and the human experiences those measures may miss.
04Stress Test & ReviseChallenge assumptions, find weak points, and strengthen the plan.
We test the plan against the mission and real operating conditions: incomplete data, edge cases, unreliable dependencies, security risks, and constraints on cost, time, and maintenance.
What could fail? How would we notice? How would we recover? What are we assuming without enough evidence?
The depth of review matches the stakes. Where decisions affect people, we also consider missing perspectives and how mistakes can be challenged or corrected.
05Build & ImplementPut the agreed improvement into practice.
I lead the initial build or configuration, check the important behavior, and bring the team into an early usable version. We document decisions as the work develops.
06Test & LearnUse it, improve it, and learn together.
Your team uses the system in real work. I make revisions, explain how it works, and guide you through managing it and making appropriate changes yourself.
07EvolutionKeep learning and building on the foundation.
Keep the system useful as your work changes. Carry lessons forward, keep documentation and playbooks current, and build on the foundation as new needs emerge. We agree on what your team can manage independently, when further review is useful, and how ongoing support can help.
Are we willing to abandon a feature when the people it affects show us that it harms them?
People need a voice in the systems that shape their work. That includes a way to question, correct, and change what we build.
Responsibility
Own our decisions and their consequences.
Security
Protect the people, information, and systems entrusted to us.
Quality
Build carefully, verify the work, and make it maintainable.
A solution you can use.
A system you can understand.
The ability to keep building.
Learning begins while we build. The handoff gives your team the knowledge and practice to carry the work forward.
Your working system
The agreed improvement, access, operating instructions, and clear responsibility for each part.
A map of the work
The people, tools, information, relationships, and decisions that make the system understandable.
Tailored playbooks
Repeatable ways to run tasks, supply context to AI, check output, and test an appropriate change.
Decisions & corrections
What was decided, how certain we were, what was missing, and why—plus a way to challenge facts and interpretations.
Guided practice
Your team completes real tasks and manageable variations, with a clear way to check and recover from changes.
A rhythm for improvement
Testing, blind-spot reviews, cleanup, and upgrades. Independent work and further support have agreed boundaries.
A workspace in development
Garden
I'm developing Garden to bring context, playbooks, and guided changes into one workspace. Its intended role is to help teams keep building. We’ll choose the tools and level of support that fit your team and the work.
The learning loop behind the work
Learn from actual use, revisit assumptions, and make deliberate improvements. Capture what the team learns so the system and its playbooks develop together.
The engineering behind this includes ontology—the map of your world—along with graphs, feedback loops, and first-principles thinking. The goal is a method your team can understand and use.