Is this a fit?
The quickest way to know is a short conversation. This page sets out what usually makes an engagement work, so you can judge before you write.
Who usually calls
Most engagements are commissioned by one of these people:
- An IT infrastructure manager
- Responsible for an environment that has to keep running while it changes.
- A security manager
- Who needs an architecture tested, documented or made defensible.
- A head of operations
- Whose team carries the consequences of decisions made elsewhere.
- A CIO or CTO
- Facing a decision that needs an independent technical reading.
- A project sponsor
- Responsible for a modernization, and accountable for its route.
Situations that often start the conversation
Not every organization has these problems. These are the ones that most often lead to a call, and where each usually goes:
| A key expert leaves, and undocumented knowledge is exposed. | Document the environment with the people who remain, or start with an Infrastructure Clarity Sprint. |
|---|---|
| A recurring incident is consuming the team's time. | A structured diagnosis. |
| A platform refresh, contract renewal or migration decision is approaching. | A Solution Design Sprint, or a Modernization Partnership. |
| The team inherited a complex environment and is unsure where to start. | An Infrastructure Clarity Sprint. |
| A solution has been bought, but the team needs design guidance or operational confidence. | A design review, and enablement for the team. |
What a good start needs
Before a proposal is written, five things are established together:
- A problem
- A specific decision, risk or capability gap, with its business impact.
- A sponsor
- An owner who can convene the participants and unblock access.
- Evidence
- The configurations, diagrams, logs and process material that exist.
- Readiness
- Access, security permissions, review capacity and timing.
- Commercial fit
- The budget process, the buyer, the urgency, and a realistic next step.
When I will suggest a different shape
Some expectations cannot be met honestly in the form they arrive in. I will propose re-scoping, or waiting, when an engagement would depend on:
- An unlimited audit.
- Guaranteed recovery.
- An enterprise-wide redesign within a short sprint.
- Production access that has not been approved.
- An outcome that depends on stakeholders who are not available.
When the uncertainty is too large to quote
A short, paid discovery phase can resolve it first: enough work to know the boundary, the evidence and the people, before anyone commits to a larger delivery.
For integrators, resellers, vendors and training organizations
If you need an independent technical specialist or instructor for one of your own engagements, I work with partners too. The same rules apply: a named scope, disclosed responsibilities, and independence in what I write.