Background Image
THOUGHTS

From “Tell Developers What To Build” To “Co‑Create With Machines”

May 6, 2026 | 5 Minute Read

For years, many business-side roles like product owners, product managers, marketers, sales, and finance partners have centered on deciding what to build and then translating that into requirements and roadmaps for developers. Generative AI cracks that model wide open.

Today, tools can already:

  • Analyze huge volumes of customer feedback and market data to surface unmet needs and trends that would take humans weeks.

  • Turn plain-language feature descriptions into prototypes, flows, or even working starter code.

  • Continuously monitor competitors and usage patterns to recommend roadmap adjustments in near real-time.

That means the “business side” isn’t just handing requirements to engineering anymore; they’re working side by side with AI systems that can generate options, simulate outcomes, and challenge assumptions just as quickly as humans can articulate them.

The New Business-Side Job: Orchestrate Value, Not Artifacts

When AI can draft specs, generate wireframes, write copy, and even scaffold features, the artifacts you create are no longer the primary value you bring. The center of gravity shifts to:

  • Judgment: Choosing which of the AI-generated ideas actually align with your strategy, ethics, and brand.

  • Framing: Asking sharper questions so AI outputs are useful, not generic.

  • Storytelling: Turning a sea of AI-augmented data into a narrative that executives, customers, and teams can act on.

In other words, your impact is less about “Can I personally write every user story, deck, or campaign?” and more about “Can I reliably steer this human+AI system toward better decisions and better outcomes?”

How AI Is Changing Business-Side Work

Area | What changed with AI

Discovery - AI clusters feedback, spots trends, and suggests opportunities.

Strategy & roadmap - AI tracks market moves and adoption, recommends shifts in priorities.

Requirements - Plain-language ideas become drafts of stories, flows, or code.

Go-to-market - AI drafts messaging, variations, and localized content at scale.

Analytics - AI surfaces patterns and anomalies automatically.

Thumbnail - From “Tell Developers What To Build” To “Co‑Create With Machines”

Tip 1: Become An Excellent Prompt Engineer For Business, Not Just For Tools

If your job involves words—backlogs, marketing copy, competitive analysis, financial models—you now have a second team member who never sleeps and works entirely in text: generative AI.

Three practical moves:

  1. Turn every recurring task into a reusable prompt.

    Take one thing you do weekly—say, summarizing customer interviews—save a prompt that turns raw notes into: key themes, verbatim quotes, potential opportunities, and risks. Treat this prompt like a template you refine every week.

  2. Design prompts that reflect your product strategy.

    Instead of asking, “Generate feature ideas,” ask, “Generate feature ideas that increase activation within 7 days for first-time users in mid-market accounts, given this north star metric and this positioning.” You’re training the assistant to think like your product.

  3. Always pair AI output with a simple decision rule.

    For example: “I’ll only accept ideas that improve this specific metric, match this ICP, and can be tested within one sprint.” This keeps you out of the rabbit hole of endless options and anchors you back to outcomes.

This is where your actor playing a developer persona is actually an advantage: you can unapologetically “over-direct the scene,” rewriting prompts, iterating on tone, and experimenting with different “scripts” until the assistant starts hitting your mark consistently.

Tip 2: Lean Into Cross-Functional AI Experiments, Not Solo Heroics

The organizations getting the most from AI right now are treating it as an operating system change, not a personal productivity hack. That’s where business-side team members can shine as connectors.

Three experiments you can lead:

  1. AI-augmented discovery days.

    • Morning: Humans interview customers, review analytics, and articulate key questions.

    • Midday: AI clusters feedback, generates themes, and drafts hypotheses.

    • Afternoon: Cross-functional group (PM, dev, UX, marketing, sales) debates the AI-generated insights and chooses 1–2 testable bets.

  2. Backlog refinement with AI as a “junior analyst.”

    Feed the assistant your product vision, definition of done, and key metrics, then ask it to propose refinements, edge cases, and risks for upcoming backlog items, but let the team critique its work out loud. You normalize AI as a draft generator, not a decision maker.

  3. AI-assisted GTM working sessions.

    Sit down with marketing and sales, give the assistant a segment, a value prop, and an objection set, and have it generate message variations, outreach scripts, and FAQ drafts to test. Your superpower here is curating and pruning, not writing everything from scratch.

In each of these, you’re using your business context and coaching mindset to make AI safer and more valuable for the whole team, not just more convenient for yourself.

Tip 3: Upgrade Your Career Story From “Role” To “Capability Stack”

Generative AI is blurring the edges between roles. Product people are prototyping, marketers are playing with data, sales is running micro-experiments, and developers are editing AI-generated code instead of writing every line themselves. Think “comb-shaped” more than “T-shaped”: deep in one area, capable across many.

On the business side, that means:

  • Stop anchoring your identity to your current title.

    Instead of “I’m a product owner” or “I’m a business analyst,” try “I’m great at discovering customer problems, framing experiments, and aligning stakeholders. I use AI as a force multiplier in each of those.”

  • Deliberately add one new spike that AI enables.

    For example, if you’re strong in discovery and roadmapping, use AI to help you get competent at basic UX flows or simple data analysis on your own. You don’t need to be the best in the room—you just need to be

    dangerous enough

    to collaborate more effectively.

  • Tell your story in terms of outcomes, not tasks.

    “I led an AI-assisted discovery and prioritization approach that increased experiment throughput 3x and helped us sunset two low-ROI initiatives” plays much better in the new world than “I wrote user stories and coordinated releases.”

This is also how you de-risk your career: roles will shift, but high-value capabilities like framing, synthesis, facilitation, and ethical judgment age well in an AI-heavy environment

Ready to rethink how your business and product teams work with AI, contact Improving to explore what it looks like to turn human + AI collaboration into real business outcomes.

Software Development

Recent Thought Leadership