
Map your current bottlenecks for automation
You'll have a visual diagram (hand-drawn, Miro, or Figma) showing your typical coding workflow with 3-5 steps marked as 'agent-ready' and 3-5 constraints (security, approval, handoff) that your harnes
What you'll make
Automation Readiness Map
- Current workflow: your typical coding process from idea to deployed code
- Agent-ready zones: 3-5 steps where AI could take over with clear input/output
- Human-required checkpoints: decision points, approvals, or judgment calls you must keep
- Constraint boundaries: security, process, or technical limits that shape automation
- Next experiments: 2-3 specific automation tests to try in the next month
Upload a photo of your hand-drawn diagram, or export from Miro/Figma/similar tool
The 4 parts
Each part ends with a check you can see.
Break Down Your Coding Process
Map out your actual coding workflow step by step, focusing on the handoffs and decision points you experience
Done when
You have a step-by-step map of your real coding workflow with at least 8-12 concrete steps from task assignment to deployment, with clear input/output for each step
Inventory Your Constraint Environment
Identify the specific rules, policies, and requirements that govern how you can change or deploy code
Done when
You have a list of at least 5 specific constraints with trigger conditions and enforcement mechanisms that limit automation in your environment
Test Each Step for Agent-Readiness
Develop your own criteria for automation readiness and apply them to each workflow step
Done when
You have 3-5 workflow steps marked as 'agent-ready' and 3-5 marked as 'human-required' with your reasoning for each classification
Choose Your First Automation Tests
Design 2-3 specific automation experiments based on your analysis and create your visual workflow map
Done when
You have a completed visual diagram and a ranked list of 2-3 automation experiments with your own success criteria and learning goals for each
Capstone: you put together your Automation Readiness Map.
Where this helps
An elective: a single lesson that sits outside rtwo's job certificates and doesn't count toward one.
About this lesson
What you'll be able to do
- Identify 3-5 specific bottlenecks in your current coding workflow where AI agents could take over immediately
- Map the constraints (security, approval, handoffs) that determine what you can vs cannot automate in your real environment
- Have a visual workflow diagram that shows where you stay in the loop vs where agents can run independently
- Know your next 2-3 automation experiments to try based on actual workflow analysis
Who it's for
- Developers who write code regularly and want to identify where AI agents could reduce manual work
- Technical leads who need to understand team automation opportunities without breaking existing processes
- Anyone curious about the transition from writing code to orchestrating AI agents
What it won't cover
- How to set up or configure Claude Code or other AI coding tools
- Detailed prompt engineering for coding tasks
- Replacing your entire development workflow immediately
- Security policy changes or approval process redesign
Skills you'll practise
- Workflow decomposition for automation targeting
- Constraint identification in technical environments
- Visual mapping of human-AI handoffs
- Bottleneck prioritization for automation experiments