R
This is really great Mike - I'm so proud of your efforts here!
15 Matching Annotations
- Last 7 days
-
research-ai-enablement-plan.netlify.app research-ai-enablement-plan.netlify.app
-
-
Research's Strategic Position
I like the emphasis on trust. One thing that may strengthen the full story is distinguishing more explicitly between what we are ready to operationalize now/soon vs. what still needs sharper conceptual validation/alignment before broader buildout (i.e., not everything is equally mature)
-
Behavioral System
this is where I still have the most questions - how is this to differ from other teams' work (DS, prod ops) and from other work within the team (holistic UX measurement)? Feels like creating overlapping systems currently.
-
Track 2: Signal Stack
one place I find myself wanting sharper definition is what makes each signal stack component meaningfully distinct - both from each other and from other efforts within the team/company. clearer boundaries would strengthen the strategy.
-
Action Plan
the pacing here feels very thoughtful - enough structure to create momentum without making AI adoption feel like extra burden. the activation rhythm in particular I like!
-
Behavioral analysis pipeline
what is this? and is DS looped in?
-
Survey:
Can I review a draft before this goes out?
-
AI Playbook / Inventory (Susannah, Ian, Angeline) — cataloging current AI use cases, workflows, and patterns across the team. This work is a potentially strong input to the Research Acceleration and Operating Model stacks.
Appreciate you proactively pulling this work in. Would love for us to really operationalize where it fits in to the broader model so that they can get un-stuck and keep making progress
-
Team may decide not to pursue — valid outcome.
synthetic users are happening in the company whether we decide to pursue or not! let's chat in our 1:1 so I can catch you up on where I'm at here with some other leaders
-
Week of April 14: Confirm Claude Code/Cowork access for all. Demo of Granola team folder + research site generation workflow.
Add to the meeting agenda please
-
Two parallel tracks that reinforce each other. Track 1 creates the conditions for Track 2. Track 2 gives Track 1 a purpose beyond individual fluency.
really strong framing here - the two track structure makes the near-term enablement work feel purposeful rather than disconnected from longer-term system building.
-
Prototype-First Pilot
appreciate this bird's eye view across! suggest having each of these link out to a more detailed doc.
-
Builder
explain what 'builder' means
-
Messages from top 5 power users
not sure what this means
-
32
Small suggestions: make this into % (since I'm not sure what the denominator is); leave %'s as whole numbers (no need for decimals), and be clear whether each number is about the research team or design org (the wording under "situation assessment" suggest research team, but the first % is clearly design org)
-