What needs to become true?
Tell me the outcome, when it matters, and what is currently preventing it. These are the situations where I’m most useful.
- We committed to something important and the architecture still isn’t settled.
- The prototype works. The path to production doesn’t.
- The previous implementation failed.
- Product, design, and engineering each own a piece. Nobody owns the whole path.
- We need to find out whether something difficult can actually be made real.
Ways to shape the work
Scope, authority, timing, and fee need to be agreed for the actual problem.
Assessment
Start with a paid investigation: the commitment, risks, architecture, and a written path. Agree the scope and fee before work begins.
Delivery
Define the critical system and own the path through working implementation, with explicit acceptance and transfer boundaries.
Embedded
Stay involved where the problem recurs and continuing product or technical authority is useful. Define that authority and the conditions for handoff.
Fit
- The outcome matters and the system is not obvious.
- The work crosses product, design, and engineering.
- A prototype or failed implementation needs a credible path to operation.
- Nobody owns the complete critical path.
- The problem is fully specified and the primary need is implementation capacity.
- The job is primarily coordination inside a large organization.
- There is no authority to change the underlying system.
Start with the commitment
Send the outcome, deadline, blocker, and any relevant context you can share. The next conversation is about whether the problem fits, what access and authority it needs, and whether assessment or delivery is the right starting point.