Strength
He investigates symptoms across code and user behaviour, then explains the uncertainty in his proposed fix.
Illustrative example · Junior software developer
Ben: proving the thinking behind the code.
Ben has been a developer for 18 months. Coding assistants help his team produce fixes and tests faster, including the small tasks he has relied on to learn. He wants his work to show more than a finished change.
01 · Profile
Where the work sits.
He fixes bugs, adds features and tests software. Diagnosing a problem often means reading logs and checking how a change will affect users before he writes any code.
Primary: Digital Builder
Secondary: Analyst
Supporting: Output Creator
Desired: Professional Advisor
He wants to grow into technical advice as he builds experience and trust.
02 · Personal AI-Era SWOT
Four findings that shape the response.
Ben chooses the signals that matter in this working situation.
Weakness
He sometimes accepts generated code before tracing its logic, and he has limited experience explaining product trade-offs.
Opportunity
AI can help him compare approaches and edge cases while his reviews and tests demonstrate sound technical judgement.
Threat
If simple implementation work shrinks, junior developers may have fewer chances to learn and prove what they understand.
His challenge is to use the speed of AI without losing the practice that builds real understanding.
03 · Goal
Long-term direction.
Over the next year, become trusted to explain technical choices in product decisions, especially their user impact and delivery risk.
His bug investigations and technical explanations give him a starting point. Trust will grow through repeated examples across product work.
04 · Action and review
Test the direction in real work.
First actions
- Write two short decision notes from real product work, showing the options, tests and trade-offs.
- Ask a senior developer and a product manager what each needs to decide from the note.
- Check AI-suggested options against the codebase before recommending one.
What the review revealed
Ben completed one decision note at his first review. A senior developer found its technical trade-off useful, but the product manager found it too abstract. He rewrote the note around user impact before preparing the second.
Next move: He keeps the long-term goal and seeks product feedback on the revised format. The decision conversation will tell him more about his progress than a count of finished notes.
What this illustrates
The value behind the visible work.
Generated code can look finished quickly. Ben makes the diagnosis, testing and consequences visible so others can trust the work.
For the wider pattern, see Digital Builders. Your own Profile and SWOT will depend on what is happening in your work.
Meet the five peopleMake the process your own
Build a plan for your work.
These pages show ADAPTOR in action. Be an AI-Era ADAPTOR gives you detailed guidance and a companion workbook for working through your own Profile, SWOT, goals and actions.