How we work with your team.

We work on the ticket in front of you

Bring one current ticket and the pod’s latest artifact to each session with us. Together, we look at the decision, the changed behavior, and the evidence. You leave with a small next action, its owner, and a check-in point. A session has earned its time when the pair can move a real piece of work forward.

Kickoff: make the first week workable

We start with the sponsor and pilot pod. A proposed 45-minute kickoff gives us time to agree the work and surface gaps. We confirm protected time for two engineers, 0.5 Product Manager, 0.5 QA, and 0.5 Program Manager per pod. Our team’s coaching and your sponsor support both pods.

1. First 10 minutes: agree the delivery problem and choose a representative ticket.
2. Next 15 minutes: check repository access, approved tools, existing safeguards, and who can unblock missing permissions.
3. Next 10 minutes: agree baseline definitions and locate the records the team already has.
4. Final 10 minutes: book the deep standup and advisory reviews; assign the first preparation actions.

We finish with named owners for gaps. If the pair cannot run or review the work yet, we resolve that in Prepare before moving on.

Two advisory reviews each week

In the first review, we challenge a specification or implementation plan with the pair: “Which decision did you settle together? Which assumption still needs an answer?” We inspect one failure case before discussing more generation.

In the second review, we inspect what happened. The engineer who did not implement the change explains it. We compare the intended behavior with the diff and check results, look at rework and obstacles, and choose one improvement for the next ticket.

You leave with a short closing note: decision made, next action and owner, evidence to bring back. We agree session length around the decision that needs attention.

At a phase checkpoint

We review the phase’s actual output together: readiness in Prepare, shared specification in Execute, review evidence in Guardrails, an independent explanation in Trust, and receiving-pod feedback in Scale. The worked examples make expectations concrete.

We ask what the pair can now do independently. We decide whether to progress, repeat a smaller exercise, or repair a specific gap, and record the reason and next owner. Delivery and quality evidence goes to the sponsor before the rollout expands.