Skip to main content
Skip to content
Menu

Development teams Beginner 3 parts

Compose a 3-part audio memo documenting your team's current AI workflow blockers and AI-powered fixe

You'll have a 10-15 minute recorded voice memo where you identify three friction points in your team's development cycle and propose how Claude or similar tools could reduce them—suitable for sharing

What you'll make

Team AI Workflow Assessment Memo

  1. Opening: The workflow friction that costs you most
  2. Problem 1: Specific friction point and AI solution
  3. Problem 2: Specific friction point and AI solution
  4. Problem 3: Specific friction point and AI solution
  5. Close: Implementation priority and next steps

Upload your recorded audio file (10-15 minutes) discussing three specific workflow blockers and AI solutions

The 3 parts

Each part ends with a check you can see.

  1. Document Your Team's Workflow Friction

    Identify and categorize the specific places where your team's development process slows down or breaks

    Done when

    You have a ranked list of 5-7 workflow friction points with concrete examples and time impact estimates

  2. Prototype AI Solutions for Top Friction Points

    Take your three highest-impact friction points and test how AI tools could actually address them

    Done when

    You have tried AI approaches on 3 specific friction points and can describe what worked, what didn't, and what implementation would require

  3. Record Your Team AI Assessment

    Create a voice memo that presents your findings in language your team will recognize and act on

    Done when

    You have a 10-15 minute audio recording that covers three friction points, AI solutions, and implementation realities in your team's context

    Capstone: you put together your Team AI Workflow Assessment Memo.

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

  • Record a 10-15 minute audio memo identifying 3 specific workflow friction points and AI solutions your team could implement
  • Demonstrate how to articulate AI adoption opportunities in language that resonates with your team's actual pain points
  • Have a tested approach for proposing AI workflow changes that acknowledges implementation realities

Who it's for

  • Development team leads who see AI potential but need to communicate it clearly to their team
  • Engineers who've experimented with AI tools personally but haven't scaled adoption across their team
  • Anyone who needs to make the case for AI workflow changes without overpromising or underdelivering

What it won't cover

  • Detailed technical implementation of specific AI tools
  • Team reorganization or role redefinition
  • Budget approval processes or vendor selection
  • Measuring long-term productivity gains

Skills you'll practise

  • Friction point identification in development workflows
  • AI solution mapping to real team constraints
  • Stakeholder communication for technical changes
  • Implementation risk assessment