AI DevelopmentRedpoint (Tomasz Tunguz)

Not Prompts, Blueprints

Read original

Why I picked this

Ties to what I wrote on executing PRDs and long running loops

ai-coding-toolsai-writing-workflowsautomation-stackspkm-workflows

“Not prompts. Blueprints. I sketch the workflow before I touch the machine. I anticipate the decision branches before the agent encounters them.”

Key takeaways

  • AI capability evolution enables shift from sequential prompting to parallel workflow execution - models can now 'hold complex tasks in their heads' vs a year ago
  • User behavior must evolve from reactive (prompt-response-prompt) to proactive (blueprint-then-execute) to unlock true leverage - planning upfront eliminates human bottleneck
  • Visual workflow blueprints (hand-drawn diagrams) work effectively as AI inputs - anticipating decision branches and edge cases before execution is the new skill
  • Real example: VC workflow (meeting notes → email → CRM → memo) now runs autonomously in background after single blueprint input vs iterative micromanagement

Why this matters for operators: Knowledge workers and operators designing AI workflows; shift from prompt engineering to workflow architecture

I cover AI×GTM intelligence like this every Wednesday.

Get STEEPWORKS Weekly

More picks

Human-AI Intersectionr/ClaudeAI

The AI not just fired us, It made our team irrelevant.

  • AI analytics tools are enabling 7:1 team consolidation in data/insights roles - entire teams replaced by single maintainer plus AI
  • Implementation pattern: consultant extraction of institutional knowledge → 3-month tool deployment → team elimination
  • The 'AI doesn't have a salary, neither a family that has to eat' framing reveals the economic inevitability companies are acting on, regardless of human impact
ai-displacement-analyticsai-workforce-impactai-consolidation
Read original Full analysis →
GTM Ops**The GTM NewsletterVictor's pick

116 Quarters on Quota and What Every Sales Leader Should Be Tracking, with Bill Binch, Operating Partner at Battery Ventures

throughback reminder its still about executing the basics

  • The 'mojo metric' framework: 6 daily pipeline inputs that predict revenue momentum before lagging indicators show problems - operational leading indicator system for sales health
  • 5-quarter look-back is the most critical board slide - provides pattern recognition on execution consistency vs one-time wins, separates sustainable growth from lucky quarters
  • Battery's anti-playbook approach: doesn't force one-size-fits-all across portfolio, evaluates operational rigor first then adapts frameworks to company stage and market - contrarian to typical VC operating model
back-to-basics-gtmhuman-first-salesrevenue-platform-consolidation
Read original Full analysis →

This analysis was produced using the STEEPWORKS system — the same agents, skills, and knowledge architecture available in the GrowthOS package.