Readiness Assessment — Pre-Session Intake

01 / 05

Your Team

Basic context so we start the session already oriented to your situation.

Q1 Your name and role * Please enter your name and role.

Q2 Who else will be joining the session from your side?

Name and role for each person. Leave blank if it's just you.

Q3 How large is your engineering team? *

1–5 engineers 6–15 engineers 16–30 engineers 30+ engineers

Please select your team size.

Q4 What is your primary tech stack? *

Be specific — languages, cloud platform, key frameworks.

Please describe your tech stack.

SECTION 1 OF 5

02 / 05

AI Tool Adoption

Where your team is on the AI adoption curve — and what that means for your delivery process.

Q5 Which AI development tools is your team currently using?

Select all that apply.

Q6 How would you describe your team's current level of AI tool adoption? *

Just getting started — a few engineers experimenting Moderate — most engineers use AI tools on some tasks High — AI tools are part of our standard daily workflow Not yet adopted — but it's on the roadmap

Please select your adoption level.

Q7 ★ When a developer uses AI to scaffold a feature, how does that change how the work moves through your sprint — if at all? *

This is the most important question on the form. Take a moment with it. Be candid about what actually happens, not what's supposed to happen.

Please share what happens in practice.

SECTION 2 OF 5

03 / 05

Your Current Process

How your team actually plans and ships work — on paper and in practice.

Q8 ★ Paste or describe your current Definition of Done. *

If you have a written DoD, copy and paste it here. If it's informal or lives in someone's head, describe what done actually means in practice for your team.

Please describe your Definition of Done.

Q9 Walk me through what sprint planning looks like for your team. *

Who's in the room? What do you actually do? How do you decide what goes into a sprint?

Please describe your sprint planning process.

Q10 What metrics does your team track to know if you're delivering well?

Be specific — velocity, deployment frequency, change failure rate, MTTR, anything you actually look at.

SECTION 3 OF 5

04 / 05

Production & Risk

How your team thinks about production confidence — especially when AI is generating the code.

Q11 Describe your last significant production incident.

What caused it — a build problem, a process problem, or something else? If you haven't had one recently, describe the closest thing to a near-miss.

Q12 ★ When AI-generated code goes to production, what is your current process for deciding it's trustworthy enough to ship? * Please describe your AI code trust process.

Q13 On a scale of 1–10, how confident is your team in AI-generated code going to production?

10 = fully trusted, no additional review needed. 1 = we wouldn't ship it without extensive manual review.

1 — Low trust 10 — Full trust 5

Q14 Where would you want that confidence score to be in six months?

1 — Low trust 10 — Full trust 8

SECTION 4 OF 5

05 / 05

What You Want From This Session

Help us calibrate the session to what matters most to you.

Q15 What's the single biggest delivery challenge your team is facing right now? * Please describe your biggest challenge.

Q16 What would a successful outcome from this assessment look like for you? * Please describe your expected outcome.

Q17 Anything else you want Jacques to know before the session?

Team dynamics, past transformation attempts, organizational constraints, anything on your mind.

SECTION 5 OF 5

Let's get you ready for the session.

Your Team

AI Tool Adoption

Your Current Process

Production & Risk

What You Want From This Session

You're all set.