Infrastructure Clarity Sprint
For a critical application delivery or security environment that is poorly understood, or understood by too few people.
- Length
- Two weeks
- Capacity
- Up to 10 working days
- Scope
- One agreed environment or technology domain
- On site
- Days agreed in advance
Who it is for
An IT manager with a critical application delivery or security environment that is poorly understood, or that depends on a few people who know how it works.
The engagement
Two weeks, up to ten working days, covering one agreed environment or technology domain. Which of those days are spent on site is agreed in advance.
Included
- A kickoff with the sponsor.
- Review of the material that already exists.
- Up to five stakeholder interviews.
- One current-state architecture diagram.
- A findings and assumptions register.
- A prioritized action backlog.
- A 90-minute management readout.
- A two-hour knowledge-transfer session for the team.
Not included by default
- A complete asset inventory.
- Changes to production.
- Penetration testing.
- Formal compliance certification.
- A detailed redesign.
What you provide
- A sponsor.
- Knowledgeable participants.
- Timely access.
- An identified reviewer.
How the two weeks run
| Stage | With your team | Evidence or output |
|---|---|---|
| Days 1–2 | Sponsor kickoff and interviews | Scope baseline and evidence request |
| Days 3–5 | Technical walkthroughs | Current state and emerging findings |
| Days 6–8 | Validation with technical owners | Diagram and prioritized backlog |
| Days 9–10 | Management readout and team session | Reviewed outputs and next steps |
Illustrative. The plan is fitted to your calendar and your access before the sprint starts.
How it is accepted
The agreed diagram, findings register and backlog are delivered; the named reviewers have a defined review window; factual corrections are incorporated within the agreed revision allowance.
Acceptance does not require every risk to be fixed. The sprint makes the risks visible and puts them in order; fixing them is the next decision.
If it is useful, what comes next
A separately scoped Solution Design Sprint, a documentation extension, or a quarterly advisory engagement through a Modernization Partnership.
Modules that can be added
Scoped and priced with the sprint, when they are needed:
- Documentation: runbooks and an ownership map beyond the single diagram.
- Diagnosis: a structured investigation of a problem found along the way.
- Enablement: a longer walkthrough, or coaching for the team.
In other people's words
Rodolfo did a tremendous job creating the Technical Library at Riverstone. The knowledge base created by him became the central repository for all technical documentation inside Riverstone (both public and confidential), not only allowing the whole organization to easily find any technical document, but also introducing a culture of documenting everything to make it available to everyone.
Rodolfo Nützmann, independent technical advisory: , https://nutzmann.net/offers/infrastructure-clarity-sprint/