The Best Product Managers Are Looking Down

The Paradox Every PM Knows But Rarely Names

Ask any product manager what their most valuable work is, and they'll tell you: talking to customers, analyzing markets, measuring outcomes, making strategic decisions. The work that happens heads-up—eyes on the horizon, thinking about where the product should go next.

But ask that same PM where they actually spend their time, and you'll get a very different answer: writing detailed specifications, grooming backlogs, clarifying acceptance criteria, updating Jira tickets, explaining edge cases to engineering.

This isn't a time management problem. It's not about being more disciplined or more efficient. It's a system design problem.

The Heads-Up/Heads-Down Trap

The best product managers I know are trapped between two opposing forces:

On one side, leadership expects heads-up work:

• Market analysis and competitive positioning
• Customer discovery and validation
• Outcome measurement and impact assessment
• Strategic roadmap planning
• Cross-functional alignment

On the other side, engineering needs heads-down precision:

• Detailed user stories with acceptance criteria
• Complete edge case documentation
• API contracts and data models
• Performance requirements and SLOs
• Compliance and security considerations

These aren't competing priorities. They're opposing forces. The more time you spend on detailed specifications, the less time you have for strategic work. And the pressure is only increasing.

Why AI Makes This Worse

The rise of AI code generation should have made this better. If AI can write code faster, shouldn't that free up time for more strategic work?

Instead, it's made the specification quality bar higher.

When a senior developer implements a feature, they bring years of context: "I know we need to handle this edge case because something similar broke in production last year." They fill in the gaps between your high-level intent and working code.

AI agents don't have that context. They implement exactly what you specify—no more, no less. If you say "add a checkout button," they'll add a checkout button. They won't consider:

• What happens if the cart is empty?
• Should guests be able to check out?
• What about users with expired payment methods?
• Do we need to log this action for analytics?

The feedback loop is faster, but the specification burden is heavier.

The Spec Gap

Between your product vision and a working feature sits the "spec gap"—all the decisions that must be made to turn intent into implementation.

Traditional approach: You manually fill the gap

• Write detailed PRDs
• Create acceptance criteria
• Document edge cases
• Update specifications during grooming
• Clarify questions during sprint planning
• Answer follow-ups throughout development

This consumes 60-70% of your time. Time that could be spent with customers. Time that could be spent on strategy.

What If There Was Another Way?

What if the interface between product intent and engineering execution had evolved along with the rest of software development?

What if you could:

• Describe user journeys at a strategic level
• Have those journeys automatically validated against your existing services and data products
• Generate complete specifications with acceptance criteria, edge cases, and dependencies
• Review and refine in minutes instead of writing from scratch for hours

This isn't about making PMs less important. It's about freeing them to do the work only they can do—the strategic, customer-facing, outcome-focused work that creates real product value.

The Question We're Exploring

In this series, we're going to explore a radical idea: What if we applied the same AI-assisted generation techniques that revolutionized code creation to the specifications themselves?

Not AI writing specs for you. AI generating specifications from your strategic intent—specifications you review and refine, specifications that are validated against reality, specifications that eliminate ambiguity before a single line of code is written.

Next up: The Spec Gap - We'll walk through a real example showing exactly what gets lost in translation between product intent and engineering execution, and what it costs.

---

This is Part 1 of the "Look Up" series exploring how AI is finally freeing product managers to do their best work.