- Core
- 20 min
- 10 min read
After this lesson you can
- Name the six Dojo Readiness areas in plain words.
- Find the rubric rows that show each area in your own work.
- Say which areas the two rubrics do not score yet.
- Use one shared language with your coach when you talk about being ready.
Read these first
Coaches look at six areas when they ask “is this learner ready?” The Dojo rubric pages use their own words. This page puts the two side by side, so you and your coach can use one language.
This page is a study aid. It is not an official assessment, an accreditation or a certificate. It does not add a score. It only shows where to look.
How to read the map
The two rubrics are close relatives. The Developer self-assessment and the Product Package rubric share the same six skills, A to F, with four levels each. The Product Package rubric also has a package checklist, a “reading the result” list and ten self-review questions. In the table, “Skill A” means row A in both pages.
Each area has one of three fits:
- Direct. A skill row describes the same ability.
- Partial. Some rows touch the area, but not all of it.
- None. No row in either rubric covers the area. The page says so and names where the area is scored instead.
The map
| Readiness area | In plain words | Developer self-assessment | Product Package rubric | Fit |
|---|---|---|---|---|
| Practical Application | You do the work with your hands and show what you made. | Skills A, C and D at level 3: a map, journeys and an epic you can show. The evidence rule in “How to use it”. | Skills A, C and D at level 3. The package checklist. Self-review question 3. | Partial |
| Reasoning | You name the problem, ask good questions, compare options and write down your choice. | Skills B, D and E, levels 3 and 4. | Skills B, D and E, levels 3 and 4. Self-review questions 1, 8 and 10. | Direct |
| Technical Execution | You finish technical tasks, write them down and leave work others can review. | Skills A and F at level 3. | Skills A and F at level 3. Self-review questions 4, 5 and 6. | Direct |
| Launch Readiness | You show the release, test, deploy and support evidence a launch needs. | No row, by design. Scored in the Track B gates and the capstone. | No row, by design. | None |
| Communication | You explain what you did, why it matters and what changed, and you say what help you need. | Skills D, E and F at level 4. The honesty check, question 3. | Skills D, E and F at level 4. The honesty check. Self-review question 9. | Partial |
| Coachability | You listen to feedback and make your work better over time. | The coach score column. “Below the target” means a coaching plan. Skill E at level 4. | The coach score column and the weekly columns. “Reading the result”. | Partial |
Every row named here exists on the linked page. Follow each link and check it.
Area by area
Practical Application
This area asks for real work, not talk. The rubrics ask for the same thing: your evidence must come from your own work, and a score with no evidence goes down one level.
The package checklist on the Product Package page is the clearest match. It lists eight parts you can make and show.
Why only partial. The rubrics score the finished work. They do not score how much you learned from practice along the way. The weekly checklists cover that: see the Track A weekly checklist.
Example (TrailMug). Her map of the product lists every repo and says what each one does. She links the file in her own git repository. That is a work sample, and it is also the evidence for Skill A.
Reasoning
This area is the best match. Each skill row asks for reasons, not only answers.
- Skill B: personas come from real evidence, not guesses.
- Skill D: each epic names a problem, an outcome and a measure.
- Skill E: the order has a reason for each place. At level 4 you also say what you chose not to do.
Example (TrailMug). She puts “deposit clarity” above “more cafés”. Next to the choice she writes the interview notes that made her change her mind, and she lists what is out of scope. That is Skills B and E, and it is the answer to self-review question 8.
Technical Execution
In Track A the technical work is planning work in your git host. Skill F is the match: epics, dates and labels are correct, and the milestones are clear enough for an agent to build from. Skill A adds the map of repos and services.
Example (TrailMug). All three epics are in the planning repo with dates and the right labels. An agent turns one milestone into a sensible list of issues. Her work can be reviewed without her in the room.
On the ladder, this is where you delegate: you hand an agent a clear brief and check what comes back. The harder hands-on tasks live in Track B. See the Track B gates.
Launch Readiness
No match. Neither the Developer self-assessment nor the Product Package rubric has a row about release, testing, deployment, support or what you show after launch. We did not stretch another row to fit.
Two other rubric pages do cover nearby ground:
- the Track B gates, especially the gate on GitOps and drift and the gate on change and incident;
- the capstone rubric, in the skills on infrastructure as code and on ITIL change and incident.
Those pages are for a later stage, and they are not part of the two rubrics on this map.
Decision, 4 November 2026: Track A gets no launch row. Three reasons:
- Track A is the planning half of the program (Developer weeks 1 to 4). You have not yet been taught to release, change or run anything, so a launch row would score work the program has not asked for.
- The launch evidence is already scored where it is taught: Track B gates 3 and 4, and capstone skills 3 and 5. A second row in Track A would score the same thing twice, at the wrong time.
- The six Track A skills are written exactly as the program defines them. This site does not add rows the program did not write.
So do not claim that a score on Skills A to F shows launch readiness. Show it in Track B and the capstone.
Example (TrailMug). Her roadmap says the returns map ships in April. Nothing in Skills A to F asks her to show a test plan, a release step or a support note. She can write those today, and her coach can look at them, but they are scored later, in the Track B gates and the capstone.
Communication
Skill D at level 4 is the clearest sign: a café owner reads her epic and says “now I understand why”. Skill E at level 4 asks you to defend the order out loud. Skill F asks you to write briefs an agent does not have to question. The honesty check asks you to explain each epic without notes. The weekly note answers “what changed”.
Why only partial. No row asks you to say what help you need. That is a good habit to add to your weekly note.
Example (TrailMug). In her weekly note she writes what she finished, why it matters for commuters, what changed since last week and one thing she is stuck on. Her coach answers the stuck point before the next checkpoint.
Coachability
The rubrics do not score this as a skill. They build it into the way you use the sheets:
- You compare your score with your coach’s score and learn from the gap.
- A score below the target means a coaching plan with dates.
- The weekly columns show whether your scores rise over time.
- Skill E at level 4 asks you to change the plan when the facts change.
Why only partial. There is a process, but no skill row with four levels. Your coach can see coachability, but the sheet does not give it a number.
Decision, 4 November 2026: the process is enough. We will not add a scored row. Coachability shows in what you do after feedback: the gap with your coach closes, and your weekly scores rise. A separate number would score the same evidence twice.
Example (TrailMug). Her coach scores Skill C one level lower than she did. She does not argue. She asks what the coach saw, adds the missing owner to one touch point, and her next weekly score matches.
The 2030 Product Development Manager lens
- You decide: which of the six areas you will show first, and what counts as evidence for each one.
- You delegate to agents: collecting your evidence, such as “list the files I changed this week”. An agent may also check your sheet for blanks.
- You verify by: opening each file the agent names. You choose the score yourself, and you say what the evidence shows.
- On the agent ladder (use, delegate, orchestrate, govern): Practical Application and Reasoning sit at use. Technical Execution reaches delegate. Launch Readiness is where orchestrate and govern start to matter, because several agents may work on a release and someone must own the rules. That is why it is scored in Track B and the capstone, where those rungs are taught. This reading is a guide for thinking. It is not part of the rubric.
Common mistakes
- Treating this page as a new score. It is a map. Use the rubric pages to score.
- Claiming a match that is not there. For Launch Readiness, say “scored in Track B and the capstone”, not a Track A skill.
- Forgetting evidence. Every area needs something you made, not a promise.
- Waiting for the coach to name the gap. Check the map yourself before the checkpoint.
- Believing this is official. It is a learning aid on this site.
Practice
- Pick the area where you feel least ready. Open the rows named for it and read the level 3 text.
- Write one sentence of evidence from your own work for each area that has a match.
- For Launch Readiness, write one thing you could show a coach today. Then find the Track B gate that will score it.
- Bring the map to your next checkpoint and ask your coach which area they would look at first.
Checklist
- I can name the six areas without looking.
- I know which rows show each area.
- I know Launch Readiness is scored in the Track B gates and the capstone, not in Track A.
- I know this page does not give a score, an accreditation or a certificate.
Where to go next
Go back to the Developer self-assessment and the Product Package rubric. Then see the Track A weekly checklist, the Track B gates and the capstone rubric.



