In short
This track is for you if you have built part of a Product Package. You now have real work to write about. You will state a point of view as one claim. Someone must be able to disagree with it. You will check every number against its original source. You will write a short post from your own work, in plain words.
Agents can draft from facts that you give them. You verify every sentence. You publish one honest write-up with the AI use disclosed. On the agent ladder, you move from use to delegate. You also prepare a correction note, in case you are wrong. Say only what you can show.
Key words
- Point of view: One claim that someone could disagree with and that your own work supports.
- AI disclosure: A plain line that says where AI helped with a piece of work. It goes in the README or the merge request.
- Brief: A written task for an AI agent, with its goal, limits and checks.
- Product Package: The final assessment of the Developer path. Eight parts.
A product owner who keeps quiet is easy to doubt. Customers, sponsors and employers cannot see how you think, so they guess. A short, clear piece of writing that says what you believe, shows the work behind it and admits what you do not know is one of the cheapest ways to earn trust. This track trains that habit and the honesty that makes it worth having.
Who this track is for
This track is for you if you have built part of a Product Package: a roadmap, a catalogue, a brand sheet, a demo or a decision record. You now have real material to write from. It suits juniors who think “I have nothing to say yet”, career changers who worry about sounding like an expert too early, and developers who now direct agents and want their judgement to be visible.
The rule that shapes this track
Say only what you can show. Every claim in a public post must trace to something you did, saw or measured, or to a source you opened and read yourself. This includes numbers. When a statistic cannot be traced to its original study, or the study cannot be opened, you leave it out. An agent will happily write a smooth paragraph with a made-up figure, so the check is yours.
The track follows its own rule. Its source material listed survey percentages with no source. We traced them to a company survey whose full report is for paying members and whose open pages do not say how many people answered. So this track uses no numbers from it. Lesson 1 shows the check.
What you will be able to do
After the three lessons you will be able to:
- Tell a point of view from a topic, a summary, a news item and a sales pitch.
- Trace a statistic to its original study, and read who asked whom, when and how many.
- Turn one part of your Product Package into a short post or demo write-up that a busy reader finishes.
- Brief an agent to draft from your facts only, and keep a claims table that links every sentence to evidence.
- Disclose AI use in one plain line, avoid hype, protect private details and publish a correction without hiding the first version.
How the three lessons build
- What a point of view is. One claim, the evidence for it, the source check and a written statement in your repository.
- Write a short post from your Product Package. Choose the part, structure the page, brief an agent to draft from facts and verify every sentence.
- Share it honestly. Disclosure, hype, private details, a human approval gate, publishing and corrections.
The lessons use the fictional product TrailMug: a point of view about where reusable cups succeed or fail, drawn from invented trial notes. Use your own product as soon as you can.
The 2030 Product Development Manager at work
At this level the manager is an author and an editor. You decide what you believe and what you will say in public. You delegate the first draft and the claim-checking help to agents with a written brief. You verify every sentence yourself and decide when it is safe to publish.
Several disciplines meet in one public post. Brand and marketing ask whether it fits the promise. Design asks whether a stranger can read it on a phone. Legal and privacy ask what you may say about customers and data. Security asks whether a screenshot shows something it should not. Finance asks whether a claim about savings is true. Support asks what people will write back.
How it maps to the Dojo
- Developer, weeks 4 and 6. Defending the roadmap and presenting the Product Package are spoken versions of the same skill. See week 4 and week 6. The write-up is a written version you can share after the presentation.
- Master Developer. The capstone asks you to show your reasoning. A short post is the lightest way to practise. See the Master Developer overview.
- The Way. The track applies Rule 5, disclose AI use. The post and its evidence live in your repository.
- Related tracks. The stakeholder communication track covers writing to people inside your project. This track covers people outside it. The decision-making track gives you decision records, good raw material for a post.
Where it sits on the agent ladder
The agent skill is a ladder: use one agent, delegate a whole task with a written brief, orchestrate several sessions, govern them with written policy and gates. Lesson 1 is on use: one agent challenges your claim. Lesson 2 is on delegate: a written brief and your own verification. Lesson 3 is on delegate and shows where govern begins: a written rule that nothing is published until a named person has checked the claims, backed by a small check in your repository.
Time needed
Plan about two to three hours per lesson, including the exercise. Leave a night between finishing a draft and publishing it.
What you will keep
You will have a folder in your repository with a point-of-view statement, a source-check log, one published write-up, its claims table, the agent brief, the review notes and a correction note. A coach, a sponsor or an employer can read it in ten minutes.
