What did product design look like in 2026?

11.18.2026

Intro

Much has been written and said about product design lately. So I took a few minutes to look back at how I’ve spent my professional time in 2026. This isn’t a complete list, but hopefully it provides some perspective about the activities, tools, and methods I’ve used designing B2B products.

Which tools I used for each activity in 2026.

Which tools I used for each activity in 2026.

Core tools

I split my time roughly 50/50 between Cursor and Figma. Between them they cover almost everything below: Figma for exploring and making visual assets, Cursor for building, prototyping, and shipping.

Strategic activities

Deciding what to build and why, and getting people inside and outside the company to buy into it.

  • Deciding which products to build
    Tools: Obsidian (writing), Cursor (prototyping), Figma (brainstorming, asset creation)
  • Setting and presenting product vision, internally and externally
    Tools: Obsidian (writing), PowerPoint (presentations), Figma (brainstorming, asset creation)
  • Building high-fidelity demos for sales conversations
    Tools: Cursor (coding, design), Figma (brainstorming, design, asset creation)
  • Building high-fidelity prototypes to explore and communicate ideas
    Tools: Cursor (coding, design), Figma (brainstorming, design, asset creation)
  • Keeping design integrated with engineering and the implementation bar high
    Methods: org alignment, process definition, standups, design reviews
    Tools: Cursor (coding, code review)
  • Making the case for the value of design
    Methods: org alignment
    Tools: PowerPoint (presentations), Zoom (meetings), Slack (async)

Tactical activities

Designing and building the actual products, features, and tools people use.

  • Designing new products and features
    Tools: Zoom (research, feedback, transcripts), Slack (feedback), Cursor (research synthesis, draft feature sets and requirements), Figma (brainstorming, wireframes, mockups, design, asset creation), Lucid (information architecture, diagrams, workflows), Confluence (final feature sets and requirements)
  • Implementing front-end design and interactions in production web apps
    Tools: Cursor (coding), Figma (asset creation)
  • Building internal tools and web apps
    Tools: Cursor (coding, design), Figma (brainstorming, design, asset creation)

Foundational activities

Building the systems, processes, and workflows that make all other design work faster, more consistent, and easier to scale.

  • Creating and maintaining design systems
    Tools: Cursor (coding, design), Figma (brainstorming, design, asset creation), Storybook (component documentation)
  • Creating team processes
    Tools: Cursor (brainstorming), Figma (asset creation), Confluence (process docs), PowerPoint (presentations)
  • Creating AI-assisted design workflows
    Tools: Lucid (diagrams, workflows), Cursor (coding, design), Figma (brainstorming, design, asset creation), PowerPoint (presentations)

Triage activities

Reactive work that fixes or rescues things that already exist, and lends expertise wherever it’s needed.

  • “Deslopifying” vibe-coded prototypes
    Tools: Cursor (coding, design), Figma (brainstorming, asset creation)
  • Making third-party web apps on-brand, usable, accessible, and functional
    Tools: Cursor (coding, design), Figma (brainstorming, asset creation)
  • Giving ad-hoc product expertise and guidance
    Tools: Zoom (calls), Slack (async)

Conclusion

The tools will probably look different next year. But across all of these activities, the value designers bring hasn’t changed: judgment about what’s worth building, a high bar for how it works, and the ability to get people aligned around it. I’m curious how this compares to what other designers are seeing. What does your list look like?