Michael Janzen

Bridging Art, Design, and Technology with a Maker's Mindset

Category: Product Management

  • A Case for the Minimalist Minimum Viable Product (mMVP)

    A Case for the Minimalist Minimum Viable Product (mMVP)

    TL;DR: Build the smallest possible app with just one core feature, launch it fast to test if your idea actually solves a real problem, then iterate based on customer feedback. Scope creep kills more projects than bad ideas—start minimal, fail fast if needed, or grow strategically based on what real users tell you.

    I’m going to out myself: I’m coming up on the 30th anniversary of building my first full-stack app. I’ve seen a lot of apps get built over the years, and I’ve witnessed the same problem again and again—the dreaded scope creep. I’m not sure if it’s more infamous as an overused cliché or as a real elephant in the room.

    I’ve seen countless projects delayed, canceled, and ultimately fail because of this phenomenon. But I’ve also seen many more succeed by following a disciplined process. Before I dive into the telltale signs and causes of scope creep, let me jump straight to a solution. (There are many ways to catch a bird—this is one of them.)

    Building Apps One Room at a Time

    Apps are built one piece at a time, like constructing a house one room at a time. Even with the budget for a giant team or multiple coordinated teams, each piece is still crafted individually. While we describe product scope with a PRD (product requirements document), when the rubber hits the road, we break things into features described through user stories and epics (bundles of stories).

    No matter the phase—design, development, quality assurance—each story is handled by one person at a time. In deeply cross-functional teams, it might even be just one person wearing multiple hats. These stories define what needs to be built at the module/component level, one step below the epic/feature.

    Most of you probably know this already, so let me fast forward.

    The Core Principle: Build the Absolute Minimum

    The principle behind a minimalist MVP: pick only what you absolutely must have to call what you’ve built “an app.” And here’s where I diverge from conventional wisdom—I’m not talking about the product you think users will adopt. I’m talking about something even smaller.

    Here’s why this matters:

    To build this first chunk requires a limited, well-defined scope that doesn’t change. This is how you compress the build timeline significantly.

    The beauty of agile development is that once you have this core chunk, you can add on—like adding rooms to a house after building the first one.

    What goes in the first room?

    • A landing page with your value proposition and pitch
    • Authentication so people can sign up
    • A payment mechanism so people can pay you
    • Legal pages to cover your obligations
    • A way for users to contact you (this starts the most important process: connecting with customers)

    Oh, and one more thing: one solid feature that you already have some verifiable certainty people need.

    Not two. Not three. Not your whole vision.

    ONE.

    Why Start This Small?

    You can build this on the lowest budget. You can build it fast. Today, using tools like Replit, you might even build it yourself without code experience (no guarantee, might not scale, might increase risk—just saying it’s possible).

    You do this because you want to fail fast if your idea doesn’t work or doesn’t solve the real human problem you set out to address the real human problem you set out to address. You do this so you can pivot to your next great idea without burning through your runway.

    But let’s say people actually like what you built. Now what?

    Now you begin engaging customers. You track their activity (within legal limits, of course) and learn from them. Customer complaints and questions tend to surface concrete product insights and questions. You’ll discover what people need, love, and hate.

    If you go deeper and start having real conversations, they’ll tell you everything you need to know about what to build next. Through the challenges they describe and the real human stories they share, patterns emerge that inform the roadmap and the real human stories they share, you’ll read between the lines and form the best ideas for your roadmap. Reading between the lines of customer stories tends to surface the most reliable roadmap inputs..

    At this stage, you steadily collect data to drive decisions. You’ll work iteratively in short sprints, adding features (and pricing tiers) to your app.

    One critical rule: Only release apps to production that are solid and deliver real value—except for that very first one. Go ahead and launch it as a BETA, preview, or pilot to start the conversations. Then, as you build new features, release them in logical bundles that feel like improvements.

    Remember: change management is real. People don’t handle change well—users adapt to change, though the disruption carries a cost in trust and engagement. Package improvements as evolution, not revolution.

    Telltale Signs and Causes of Scope Creep

    Here’s what to watch out for:

    New Ideas

    Founders are often the biggest culprits because they’re the ones with endless ideas, and those ideas come fast and relentlessly. It takes a rare, disciplined individual to harness this creative energy and focus it into manageable development chunks.

    If you’re one of these visionaries, you need a partner—someone you trust and, importantly, someone you defer to for product development decisions. This person collects every idea flowing from you, documents it, and researches market potential, complexity, cost, and benefit. Then, armed with data, they help you make informed decisions.

    Think of this person as the lens that focuses your energy. If you can find a trusted ally for this role, keep them close, build trust, and they will help you succeed.

    Changing Decisions Mid-Flight

    We’re all guilty of this. Halfway through execution, you realize your initial decision wasn’t ideal, or you’ve identified a new direction. If you’re on a limited budget, you may have no choice but to see the original plan through. But if you have financial flexibility, the temptation to pivot mid-build is strong.

    When you turn the ship during the initial build, you risk the entire MVP’s failure.

    Remember: you’re building the first chunk. Once you’re iterating sprint by sprint, pivot away—the risk is contained in time-boxes. But during the initial build phase, you’re not trying to iterate yet. You’re trying to get something into customers’ hands so they can guide you toward the successful product you envision.

    Big Vision Syndrome

    If your idea is ambitious—if you want to eventually compete with giants but know you must start small due to time, money, and reality—it’s tough to keep that vision from creeping into your current work. It’s even harder to believe this tiny thing you’re building could ever reach that giant size.

    Avoid this pitfall by compartmentalizing current work from future vision. Be disciplined. Build processes that help you context-switch between today’s execution and tomorrow’s dream.

    Big Budget Paradox

    Ample funding introduces risks that are worth naming alongside its advantages. Ample funding (angel investors, seed rounds, etc.) seems like pure upside, and it can be—but ample funding introduces its own risks worth naming.

    When money is available, it’s natural to imagine the scope can expand proportionally. It can, but you should still follow the process: build the tiniest thing possible, launch it, then iterate.

    Don’t fall into the trap of spending everything on round one. Be frugal. Build small. Add on incrementally, just like you would if you were working with friends in a garage. Bootstrap your approach even when funds are available, because the mMVP remains the fastest path to customer conversations. You’ll have an actual app to discuss—even if it’s the smallest app in the room.

    Enterprise Budget Approval Traps

    Most of my career was spent building apps in enterprise environments. I did plenty of side hustle work too, so I’ve tasted both worlds. On the enterprise side exists a problem most startups don’t face: massive budgets coupled with glacial approval processes.

    The challenge? Because approvals take so long, you must present the biggest package possible to secure funding in large chunks. So yes, do that—but when it comes time to build, still start with the mMVP. Don’t try to build the mature version in the first pass.

    Your vision and pitch win budget approval, but they don’t dictate your build approach.

    In enterprise contexts, you may not want to release publicly until you have a fully functional product. That’s a stark difference from the SaaS startup world, where you’re closer to customers and risks are lower. But even in the enterprise, launch your mini-mMVP in a test environment. Conduct user research sessions, validate direction, and gather feedback to guide iteration before the big public reveal months later.

    The Bottom Line

    No matter your size, budget, or environment: build small and fast. Get customer eyes on your product as quickly as possible. That’s the most valuable thing you can do.

    Ideas come fast and frequently. But they have zero value in product development unless you can verify you’ve hit the nail on the head—that people actually want what you’re building and will pay for it.

    No amount of research will give you that certainty. Research points you in the right direction, but customers provide the proof.

    Start minimal. Listen closely. Iterate relentlessly.

    What’s your experience with scope creep? Have you found success with ultra-minimal MVPs, or do you think there’s a “too small” threshold? I’d love to hear your stories in the comments.

  • SketchUp Collaboration: A Strategic Vision for the Future of Design

    SketchUp Collaboration: A Strategic Vision for the Future of Design

    Disclaimer: These views are my own and do not represent Trimble’s official strategy

    TL;DR: SketchUp’s collaboration initiative positions the product at a critical juncture—defending against cloud-native tools that have reset user expectations while integrating into Trimble’s enterprise ecosystem. Success requires a three-horizon strategy: perfecting lightweight review workflows now, building seamless bridges to enterprise capabilities, and pioneering new co-creation models that preserve SketchUp’s accessible soul. This document outlines that strategic framework through competitive analysis, organizational design principles, and direct product experience.

    Prologue: Why This Document Exists

    For over fifteen years, SketchUp has been my creative partner. I discovered it when it was still free and owned by Google—a revolutionary tool that democratized 3D design by making it genuinely approachable. As an early advocate, I promoted SketchUp extensively through my design blog, where I encouraged thousands of readers to use it as their go-to drawing software for architectural design. It became the foundation for my work: I began working with SketchUp nearly a decade ago, initially using it for architectural visualization projects before gradually shifting my focus toward more artistic applications. Over the years, I refined my modeling techniques and developed a distinctive visual style, which eventually led me to explore the intersection of digital design and physical fabrication — culminating in my most ambitious undertaking yet: a series of 3D-printed sculptures. Please provide the full original passage that includes the 3D-printed sculptures detail, and I will be happy to rewrite it according to the recommendation., and, most recently, have been designing complex 3D-printed sculptures that push the boundaries of what the tool can create.

    Unlike a conventional market analysis, this framework is grounded in fifteen years of hands-on use alongside direct product management experience. This comes from someone who has spent years in both worlds—as a product manager building collaborative B2B SaaS platforms and as a devoted SketchUp user who understands the software’s essence from thousands of hours of hands-on use.

    (sentence removed)

    All strategic assessments are based on publicly available information, competitive analysis, and my experience as both a product management professional and a long-time SketchUp user.

    Before writing this document, I conducted extensive research into SketchUp’s current state at Trimble—studying the recent collaboration feature releases, analyzing the Trimble Connect integration strategy, and examining how the product fits within the broader portfolio. I performed a competitive analysis of the AEC software landscape and studied collaboration best practices from adjacent domains. This document synthesizes that research into a strategic framework.

    *(paragraph deleted)* The strategic framework that follows is grounded in competitive analysis, informed by organizational design principles, and shaped by a genuine understanding of what designers need when they collaborate.

    (Sentence deleted — no replacement text.)

    The framework begins with deep user empathy, builds on rigorous market analysis, and structures solutions around measurable outcomes that matter. If this resonates with how the SketchUp team approaches product development, I welcome the opportunity to continue this conversation. Regardless of outcome, the genuine hope is that some of these ideas in this document prove useful to the team building SketchUp’s future. *(sentence removed)*

    Introduction: The Inflection Point

    SketchUp faces competing pressures from two directions simultaneously. For two decades, it has dominated early-stage conceptual design with an unparalleled ease-of-use advantage. In 2025, the competitive landscape has fundamentally shifted. Cloud-native tools like Figma have reset user expectations for collaboration, while enterprise platforms like Autodesk’s Construction Cloud have deepened their ecosystem moats. The recently launched collaboration features—private sharing, in-app commenting, and real-time viewing—represent SketchUp’s opening move in this new era. The strategic opportunity, however, extends considerably further.

    This document outlines a strategic framework for transforming SketchUp from a beloved individual design tool into the collaboration platform of choice for modern design teams. The goal is to preserve the ease of use that defines SketchUp while harnessing Trimble’s industrial ecosystem to deliver enterprise-grade collaboration without sacrificing accessibility.

    The Market Reality: Two Competitive Fronts

    The Cloud-Native Threat from Below

    The design collaboration software market is projected to grow from $3.8 billion in 2025 to $15.1 billion by 2035—approximately 15 percent compound annual growth rate overall, with cloud-based solutions (the deployment model most relevant to SketchUp’s strategy) growing at 15.3 percent annually (Future Market Insights 2025). This growth is driven by tools built natively in the cloud—platforms like Figma, where real-time collaboration is not a feature but the foundation.

    While Figma operates in a different domain (2D UI/UX design versus 3D spatial modeling), it represents a critical strategic reference point—not as a direct competitor for SketchUp’s users, but as a benchmark that has redefined collaboration standards that has fundamentally reset expectations for what collaboration should feel like. Figma reset collaboration expectations by enabling multiple people to work together in real time, much like Google Docs. Analysts observe that Figma’s model “became the gold standard” in collaborative creative software, democratizing design through browser-based access and altering expectations across all creative tools. Designers who use both Figma and SketchUp will inevitably compare the experiences. The overhead of save-export-email-review-download-revise workflows creates meaningful friction compared to sharing a link and watching cursors move in real time. Figma’s model has raised the baseline expectation for collaboration across creative tools—including those, like SketchUp, that operate in entirely different domains.

    SketchUp’s new collaboration features address this expectation directly by bringing conversations into the model itself. The current implementation—focused on review and feedback rather than co-creation—reveals an important strategic choice about what kind of collaboration SketchUp will prioritize.

    The Enterprise Squeeze from Above

    At the other end of the spectrum, Autodesk and other AEC giants are building deeply integrated ecosystems where design, documentation, and construction management flow seamlessly through a unified data environment. Autodesk Construction Cloud serves as “a unified modern platform that connects design authors, reviewers, preconstruction teams, field crews, and closeout stakeholders in one data environment,” providing centralized project documentation that enables “permit requirements and regulations to be met and maintained” while giving “real-time visibility into every stage of the project” (Autodesk 2024). Their value proposition extends beyond making better designs—it encompasses reducing project risk, ensuring compliance, and connecting designers to the downstream reality of what gets built.

    Trimble’s response through Trimble Connect is strategically sound: it positions the Common Data Environment as the connective tissue linking SketchUp’s conceptual work to the industrial-grade project management capabilities the parent company excels at. Trimble Connect “integrates project data for real-time visibility” across more than forty-five file types and serves as a cloud-based platform that “eliminates silos, improves communication and accelerates decision-making” (Trimble 2024). With over twenty-four million projects managed in the platform, it represents a mature ecosystem connecting SketchUp models to Trimble’s broader construction and engineering solutions. Integration alone is insufficient. The transition from lightweight in-app collaboration to enterprise CDE workflows must feel natural, not like jumping to a different product.

    Strategic Framework: The Three Horizons

    To compete effectively on both fronts, SketchUp’s collaboration strategy should operate across three time horizons simultaneously:

    Horizon 1: Perfect the Review Workflow (Now – 12 months)

    Strategic Goal: Make SketchUp the fastest, most intuitive platform for design review and client feedback loops.

    Key Initiatives:

    Depth over breadth in commenting. The current commenting system is good; the goal is exceptional. Enhanced features should include time-stamped comment histories showing design evolution, smart resolution workflows tracking what has been addressed, integration with common task management tools (Asana, Monday.com) for automatic action item creation, and voice comments for more natural feedback—especially valuable for nontechnical stakeholders.

    Optimize the View Scenes experience. This “slideshow mode” is brilliant for client presentations—double down on it. Add:

    • Automated scene generation using AI to suggest optimal camera angles
    • Narration recording capabilities for asynchronous presentations
    • Analytics showing which scenes received the most attention and comments
    • Customizable branding and presentation templates

    Make sharing frictionless. Every click between “I want feedback” and “stakeholder is reviewing” is a point of potential abandonment. Implement:

    • One-click sharing to common platforms (email, Slack, Teams)
    • QR code generation for in-person reviews on mobile devices
    • Guest access that doesn’t require accounts for view-only stakeholders
    • Smart defaults that remember sharing preferences per project type

    Performance obsession. Large models with multiple active viewers need to feel instantaneous. Continue the trajectory from the 86% FPS improvement in scene transitions—target another 50% improvement for model loading and navigation with multiple active collaborators.

    Horizon 2: Bridge to Enterprise Workflows (6-18 months)

    Strategic Goal: Create seamless on-ramps from lightweight collaboration to enterprise data management without forcing users to learn a new system.

    Key Initiatives:

    Progressive disclosure of Trimble Connect. Most users do not wake up wanting a CDE—they want to solve specific problems. Surface Trimble Connect capabilities contextually. When a model reaches certain size or complexity thresholds, offer automatic cloud backup with version history. When comment threads mention the same issue repeatedly, suggest linking to formal project management workflows. When multiple disciplines are involved, highlight cross-tool integration benefits. Provide in-app tutorials that activate based on user behavior patterns.

    This approach mirrors the concept of dissolving work into component parts (Wrzesniewski and Dutton 2001)—understanding what users actually do before prescribing how they should work. Rather than forcing adoption of enterprise tools, the system adapts to user needs organically.

    Unified data model. The biggest friction in enterprise tools is feeling like you are managing files rather than designs. Create a single source of truth where changes made in any connected tool automatically sync, version control is invisible but comprehensive, permission boundaries are clear but flexible, and the ground truth always resides in the cloud, not in conflicting local copies.

    Cross-platform consistency. SketchUp for Desktop, Web, and iPad currently have different levels of Trimble Connect integration. Eliminate this variance:

    • Full native integration across all platforms by end of 2026
    • Identical collaboration features regardless of where users access the model
    • Seamless handoff between devices (start on desktop, review on iPad, comment on web)

    Demonstrate ROI for enterprise buyers. IT decision-makers need different value propositions than designers. Develop dashboards and reporting that show:

    • Time saved in review cycles (measured in days or weeks)
    • Reduction in revision rounds required for approval
    • Cross-project insights about bottlenecks and efficiency
    • Compliance and audit trails for regulated industries

    Horizon 3: Define the Future of Co-Creation (12-36 months)

    Strategic Goal: Establish SketchUp’s vision for what collaborative 3D design should look like, differentiating from both BIM-heavy and 2D-focused competitors.

    Key Initiatives:

    Real-time co-modeling—with guardrails. The technical challenge of multiple people editing 3D geometry simultaneously is solvable; the UX challenge is enormous. Unlike a 2D canvas, 3D models have complex relationships between components. Develop:

    • Component-level locking that allows simultaneous work on different parts of a model
    • “Branching” capabilities for trying alternative approaches without affecting the main design
    • Conflict resolution that’s spatial and visual, not text-based like code merges
    • AI-assisted coordination that suggests complementary areas for team members to work on

    Expand AI from visualization to collaboration. SketchUp Diffusion shows the potential for AI in the creative process. Extend this philosophy to collaborative workflows:

    • AI-generated design alternatives based on comment feedback
    • Automated compliance checking against building codes or client requirements
    • Natural language interfaces for common modeling tasks (“add a door here”)
    • Predictive insights about which design elements will require the most stakeholder discussion

    Embrace asynchronous-first collaboration. Not every designer works 9-5 in the same timezone. Build features specifically for distributed teams:

    • Recorded walkthroughs with voiceover that can be reviewed on-demand
    • Change summaries that automatically generate “what’s new” videos between versions
    • Smart notifications that respect time zones and working hours
    • Persistent workspace states so jumping into a collaboration session feels like returning to an active conversation, not starting from scratch

    Mobile-first review experience. The future of stakeholder feedback is happening on tablets and phones at job sites, not in conference rooms. Make the mobile experience flagship-quality:

    • AR viewing capabilities that let clients “place” designs in physical spaces
    • Touch-optimized markup and measurement tools
    • Offline capability for reviewing models in low-connectivity environments
    • Integration with mobile photography to document field conditions alongside design comments

    The Differentiation Thesis: Design-Centric Collaboration

    SketchUp collaboration should not be a lightweight Autodesk Construction Cloud or a 3D version of Figma. The unique strategic position lies at the intersection of design creativity and constructability.

    For Designers: SketchUp should be where ideas take shape through conversation. The feedback loop between showing work and incorporating insights should be measured in minutes, not days. The tool should amplify creativity, not bureaucratize it. This aligns with what organizational psychologists call job crafting—the proactive redesign of work to be more meaningful (Wrzesniewski and Dutton 2001). Collaboration features should enable designers to craft their workflows around their creative process, not force their process into rigid templates.

    For Stakeholders: Clients, contractors, and consultants should engage meaningfully with designs without becoming SketchUp experts. The barrier to valuable input should be near zero. This is about eliminating what might be called the drudgery tax—the friction that prevents people from contributing their unique expertise because the tools demand too much cognitive overhead.

    For Enterprises: When projects scale from concept to construction, the transition to structured workflows should happen naturally, preserving early design intent and conversation history as foundational project knowledge.

    This positioning directly addresses the core tension in Trimble’s portfolio: SketchUp is loved for its accessibility; Trimble’s other products are valued for their power. The collaboration initiative should be the bridge that lets users start in the former and scale into the latter when—and only when—they need to.

    Success Metrics: Beyond Feature Adoption

    Traditional product metrics (daily active users, feature adoption rates) are necessary but insufficient. The success of SketchUp collaboration should be measured by outcomes, not outputs—a distinction famously articulated by Peter Drucker in his concept of “management by objectives” (Drucker 1954). The goal is not shipping features on schedule but creating measurable value for users.

    Time to feedback: How long between sharing a model and receiving substantive comments? Target under two hours for client reviews, under fifteen minutes for internal team reviews.

    Revision efficiency: How many revision cycles are needed to reach approval? Target a 30 percent reduction compared to pre-collaboration feature baseline.

    Ecosystem pull-through: What percentage of collaboration users eventually adopt Trimble Connect or other Trimble products? Target 25 percent within twelve months of active use.

    Retention by use case: Different user segments have different needs. Track retention separately for solo practitioners doing client presentations (high volume, lightweight usage), small design firms managing multiple concurrent projects (moderate complexity), and enterprise teams integrating with construction workflows (high complexity, high value).

    Net Promoter Score by persona: Designers, clients and stakeholders, and enterprise administrators should all be tracked separately. A designer NPS of seventy or higher is achievable—industry benchmarks confirm that NPS above fifty is excellent and above eighty is world-class (Qualtrics 2024). Anything below fifty for client stakeholders indicates friction in the review experience.

    Organizational Implications: Product and Go-to-Market

    Product Organization

    This strategy requires a dedicated team structure:

    Core Collaboration Team: Owns the in-app features—commenting, sharing, real-time viewing. Success metric: designer NPS and time to feedback.

    Platform Integration Team: Bridges to Trimble Connect and other Trimble products. Success metric: ecosystem pull-through rate.

    AI and Emerging Tech Team: Develops next-generation capabilities in Horizon 3. Success metric: innovation pipeline health and beta program engagement.

    Collaboration Design Research: A dedicated researcher focused on understanding how design teams actually work, not just how they use SketchUp. This insight drives the roadmap. This role embodies what might be called organizational anthropology—studying the native language and power structures of design teams to inform product decisions that genuinely serve their needs.

    Go-to-Market Strategy

    For Individual Practitioners: Emphasize simplicity and speed. Marketing message: “Get better feedback, faster.” Channel: content marketing showing before-and-after workflow improvements.

    For Small Firms: Position as the growth enabler. Message: “Take on bigger projects with the team you have.” Channel: case studies from successful small firms that scaled using collaboration features.

    For Enterprises: Lead with risk reduction and visibility. Message: “From concept to construction, without losing the plot.” Channel: direct sales with IT and project leadership, emphasizing Trimble ecosystem benefits.

    Community Amplification: SketchUp’s user community is one of its greatest assets. Create a Collaboration Champions program that recognizes power users who develop best practices, provides early access to new features for feedback, amplifies success stories through comarketing, and develops templates and workflows that others can adopt. This creates what General Stanley McChrystal calls a “team of teams” approach—empowering distributed networks rather than relying solely on top-down directives (McChrystal et al. 2015).

    The Critical Path Forward

    If I were leading this product initiative, here are the immediate priorities for the first ninety days:

    Days 1–30: Listen and Learn Interview fifty or more users across all segments about their current collaboration pain points. Shadow ten design teams through complete project cycles. Audit competitive tools (Figma, Onshape, BIM Collaborate) for inspiration. Map the current user journey from SketchUp to Trimble Connect—identify every friction point. This is not market research theater; it is the foundation for evidence-based decision-making.

    Days 31–60: Define and Align Create a unified vision document for what SketchUp collaboration should be in three years. Build consensus with leadership on which horizon gets primary investment. Establish clear success metrics and instrumentation plans. Recruit or identify key team members for each focus area. This phase is about creating psychological safety within the product organization—ensuring the team knows the why behind decisions, not just the what (Edmondson 2018).

    Days 61–90: Ship and Signal Launch at least one high-impact improvement to existing collaboration features. Begin beta program for Horizon 2 capabilities with enterprise design teams. Publish thought leadership on design-centric collaboration to establish positioning. Create internal alignment through roadmap reviews with cross-functional stakeholders. The goal is not perfection but momentum—demonstrating that the organization can iterate its way to excellence.

    Conclusion: The Opportunity for Transformative Impact

    The design software market is experiencing a once-in-a-decade shift. Tools that were previously evaluated on feature checklists are now being chosen based on how well they enable teams to work together. SketchUp has spent 20+ years building trust with designers as the most approachable 3D modeling tool. That trust creates permission to reimagine what collaborative design should look like.

    The collaboration initiative isn’t just a feature set—it’s SketchUp’s chance to remain relevant in an era where solo design work is increasingly rare. Done right, it can defend against cloud-native competitors while unlocking Trimble’s enterprise ecosystem value. Done poorly, SketchUp risks becoming a legacy tool used only for initial sketching before teams move to “real” collaboration platforms.

    The technical challenges are real but solvable. The strategic questions—what kind of collaboration, for which users, at what point in their workflow—are where the leverage lies. This is fundamentally a product vision challenge, not an engineering challenge. And that’s what makes it exciting.

    The path forward is clear: start by perfecting the review workflow, build trustworthy bridges to enterprise capabilities, and pioneer new models of co-creation that preserve SketchUp’s creative soul. Execute this strategy well, and SketchUp won’t just survive the collaboration era—it will define what design collaboration should be.

    This strategic framework is designed to spark conversation and refinement. The best product strategies are living documents that evolve with user feedback, market dynamics, and organizational learning. I’m excited to discuss how these ideas can be adapted, challenged, and improved as we build the future of SketchUp together.

  • Why Multi-Agent Systems Are the Next Leap in AI Integration

    Why Multi-Agent Systems Are the Next Leap in AI Integration

    TL;DR: Multi-agent frameworks like LangChain and LangGraph are transforming how we build AI systems. Instead of hand-coding endless business logic, we can now orchestrate intelligent agents that adapt, collaborate, and solve problems dynamically—unlocking new possibilities for speed, scale, and efficiency.

    From Business Logic to Intelligent Agents

    For decades, building digital products meant codifying every possible rule into business logic. If you wanted a system to handle exceptions, you wrote conditional statements. If you wanted workflows automated, you built complex process maps. This approach was powerful, but brittle—any change in business needs meant weeks or months of re-engineering.

    Multi-agent systems flip that paradigm. Instead of hard-coding logic, we deploy autonomous agents—each with its own role, memory, and tools—that collaborate to achieve a goal. With orchestration frameworks like LangChain and LangGraph, these agents can reason, call APIs, retrieve data, and even negotiate with each other to decide the best path forward. The result: flexibility and adaptability we couldn’t achieve before.

    What This Means for Business Leaders

    For senior executives, the implications are profound:

    • Faster Time to Value
      New workflows can be assembled in days, not months. A product team can stand up an AI agent that integrates with finance systems, marketing tools, or customer data—without writing thousands of lines of logic.
    • Scalable Intelligence
      Instead of centralizing every decision into a single model or system, multi-agent architectures allow specialized agents (e.g., a “legal reviewer,” a “data retriever,” a “strategy summarizer”) to collaborate. This mirrors how cross-functional teams work in business.
    • Operational Efficiency
      Multi-agent systems can automate processes that once required large teams. Think contract review, campaign optimization, or customer support triage. These are no longer point solutions but adaptive workflows that learn and improve.
    • Strategic Differentiation
      Companies that harness agentic systems can create products and experiences competitors can’t replicate with static automation. It’s not just about efficiency—it’s about creating new value.

    What We Can Do Today That We Couldn’t Do Before

    Here are just a few examples of where multi-agent systems are already changing the game:

    • Complex Decision-Making: A team of AI agents can simulate multiple strategies, weigh trade-offs, and recommend the best path—something static automation could never handle.
    • Dynamic Integrations: Agents can discover and use APIs on the fly, connecting systems without pre-defined glue code.
    • Continuous Learning: Unlike brittle business rules, agents can learn from outcomes and adjust their behavior, making operations more resilient.
    • Human + AI Collaboration: Agents don’t replace people; they extend them. Imagine a “Chief of Staff agent” preparing analysis for an executive, while a “Research agent” continuously monitors the market.

    Why Now?

    Technologies like LangChain and LangGraph provide the scaffolding to build these systems safely and at scale. They abstract away complexity—managing state, handling memory, orchestrating tool use—so product leaders can focus on business impact instead of plumbing. For companies embracing AI transformation, this isn’t a technical curiosity; it’s a competitive advantage.

    Final Thought

    Multi-agent systems represent a fundamental shift in how we build with AI. They move us from coding rigid processes to designing adaptive, collaborative systems. For product leaders and executives, the question is no longer if these systems will shape the future of work—it’s how quickly you can harness them to reshape your own business.

    🔗 This article builds on concepts I explore in my forthcoming book, Agile Symbiosis, which examines how AI is transforming professional growth and organizational design.

  • How to Spot a Polymath and Why You Should Hire Them

    How to Spot a Polymath and Why You Should Hire Them

    TL;DR: AI is ending the age of specialization, making polymaths essential hires. Their broad knowledge and adaptability help them quickly adopt new technologies and lead organizational AI transformation.

    Traditional career success relied on deep specialization in narrow fields. AI is now reversing this paradigm by democratizing knowledge and automating specialized tasks, transforming professionals into “AI-augmented generalists.” The era of hyper-specialization as the primary path to career success is coming to an end.

    In this evolving landscape, polymaths—individuals with broad knowledge across subjects—become indispensable leaders. Their adaptability and learning drive position them to embrace and leverage AI technologies effectively. As natural pioneers of AI transformation, they bridge knowledge gaps and become exceptionally powerful contributors when AI-enabled, inspiring organizational change.

    Often misunderstood, polymaths aren’t just “jacks of all trades”—they combine broad interests, deep curiosity, and a continuous learning drive. Hiring polymaths brings innovation, adaptability, and holistic problem-solving to organizations.

    So, how do you spot one? What makes them such indispensable members of a team?

    Tell-Tale Signs You’re Looking at a Polymath:

    1. Diverse Skills and Interests: A polymath’s resume might look like a collage of seemingly unrelated pursuits. They might excel in engineering, play multiple musical instruments, write poetry, and possess a profound understanding of ancient philosophy. Their library isn’t neatly categorized by genre but is a testament to their eclectic intellectual appetite.
    2. Obsessive Curiosity and a Thirst for Learning: Polymaths are lifelong learners. They don’t stop learning after getting a degree. They constantly strive to understand the underlying principles into each subject that interests them. Discovery brings them joy.
    3. Big-Picture Thinkers: Polymaths think about fundamental questions and connections between things. They care more about “why” something works than just “how” to do it. This helps them identify patterns that specialists may miss, leading to the discovery of innovative solutions by connecting different fields.
    4. Driven by Learning and Making, Not Just Ambition: While polymaths can be highly successful, their primary motivators are typically the pursuit of knowledge and the act of creation. They might embark on new ventures not for financial gain or status, but because a new idea has captured their imagination, and they feel compelled to explore it or bring it to life. This intrinsic motivation often fuels a relentless pursuit of mastery.
    5. A Little “Weird” (in a good way): Due to their unconventional interests and way of thinking, polymaths may not always fit neatly into traditional molds. They may challenge conventional wisdom, approach problems from unexpected angles, and possess a unique perspective that can sometimes be quirky or unconventional. Embrace this “weirdness”—it’s often a sign of their independent thought and creative spirit.
    6. The Ability to “Connect the Dots”: Divergent thinking is a superpower of polymaths. Their broad knowledge base allows them to draw analogies and insights from one field and apply them to another seemingly unrelated area. They can synthesize information from disparate sources to form novel solutions and understandings. Think of them as the ultimate “T-shaped” individuals – deep in some areas but with a wide breadth that allows for cross-disciplinary collaboration.
    7. Adaptability and Resilience: As they continually learn and explore, polymaths are inherently adaptable. They are not easily fazed by new challenges or shifting landscapes, as they’ve likely already grappled with diverse problems in their varied pursuits. This makes them highly resilient in the face of change and uncertainty.
    8. Initiative and Self-Direction: Polymaths don’t wait to be told what to learn or do; they take the initiative. They are proactive in seeking out new knowledge and experiences. They often have a strong sense of personal agency and are comfortable charting their course.
    9. A Love of Books and Diverse Media: While not universally true, many polymaths are avid readers, consuming a wide range of literature, non-fiction, and academic texts. They also tend to engage with various forms of media, always seeking new information and perspectives.
    10. Early Adopters and Amplifiers of New Tools (Especially AI): Polymaths quickly grasp the potential of new technologies, especially those that amplify human capabilities. They’ll be among the first to experiment with AI tools, integrate them into their workflow, and demonstrate their practical applications. Furthermore, their ability to understand diverse domains enables them to effectively communicate the benefits of AI to various teams and roles, making them crucial agents in the organization’s adoption of AI. They see AI not as a replacement for human skill but as a powerful extension, helping to transform anyone into an “AI-augmented generalist” or “augmented expert” by bridging knowledge gaps and accelerating learning. Their inherent drive to fill their skill gaps means they will naturally be the quickest to adapt to and leverage AI, leading organizational transformation.

    Why You Should Hire Them:

    Hiring a polymath is an investment in your organization’s future. Here’s why they are invaluable:

    • Innovative Problem-Solving: Their ability to connect disparate ideas leads to out-of-the-box solutions for complex challenges. They can approach problems with a holistic perspective, drawing on knowledge from multiple domains.
    • Adaptability in a Dynamic World: In rapidly evolving industries, polymaths can quickly learn new skills and adapt to technological shifts and changing market demands, making your team more future-proof.
    • Enhanced Communication and Collaboration: With their understanding of various fields, polymaths can act as bridges between different departments or specialist teams, facilitating better communication and fostering cross-functional collaboration.
    • Natural Leadership Potential: Their broad perspective, strategic thinking, and ability to understand and integrate diverse viewpoints make them excellent candidates for leadership roles. They can see the bigger picture and guide teams through complex interdisciplinary projects.
    • Cultural and Intellectual Diversity: Polymaths enrich the workplace environment by bringing a wide range of perspectives and fostering a culture of continuous learning and intellectual curiosity.
    • Increased Creativity and Productivity: Far from being “jacks of all trades, masters of none,” true polymaths can apply their diverse skill sets to enhance efficiency and creativity in multiple areas, leading to more impactful and innovative outputs.
    • Accelerated AI Adoption and Maximized ROI: Polymaths will naturally lead the charge in integrating AI tools, demonstrating their practical value, and helping others overcome the learning curve. Their ability to quickly grasp and apply new technologies means your investment in AI will yield quicker and more substantial returns, fostering a workforce of “AI-augmented generalists” and driving your organization’s AI transformation.

    In essence, polymaths are the intellectual “Swiss Army knives” of the modern workforce, particularly as AI redefines the landscape of skills and moves us beyond the era of hyper-specialization.

    While they may not always fit into conventional boxes, the unique blend of curiosity, adaptability, and interdisciplinary thinking they bring to the table makes them indispensable for any organization looking to innovate, grow, and thrive in an increasingly complex world.

    Start looking beyond the narrow specialist, and you might uncover a hidden polymath waiting to transform your team and lead your AI revolution.

  • 10 Reasons “Overqualified” Talent Is Your 8-Armed Secret Weapon in the AI Revolution

    10 Reasons “Overqualified” Talent Is Your 8-Armed Secret Weapon in the AI Revolution

    TL;DR: That “overqualified” candidate you’re hesitating to hire might be your most valuable asset. They bring cross-functional expertise, crisis-tested judgment, natural mentorship abilities, and rapid adaptability to new technologies—exactly what companies need to navigate today’s quickly evolving AI era.

    After nearly three decades building products and leading teams, I’ve developed a contrary view on hiring. That “overqualified” candidate you’re hesitating to bring on board? They might be your most valuable hire. Here’s why.

    1. Beyond T-shaped expertise

    Most hiring managers look for T-shaped professionals. I look for something different. Truly exceptional candidates are what I’ve come to call “octo-shaped.” 

    Think about it. When expertise extends into product development, engineering, design, marketing, operations, finance, business strategy, and people management, your humble eight-armed ally amplifies your team’s power.

    Their unique contribution is their depth across multiple domains, which is only acquired through experience – it can’t be taught. When technical teams speak in jargon, these folks understand. When business stakeholders worry about margins, they empathise with the concerns naturally. 

    Conflicts are commonplace, and they’ve seen, mediated, and negotiated through them all. They bridge gaps effortlessly because they’ve stood on all sides. Cross-functional collaboration isn’t a buzzword for them—it’s as natural as breathing.

    2. Risk mitigation in uncertain times

    I’ve learned that nothing reduces hiring risk like bringing on someone who’s weathered multiple business cycles. Economic downturns? Disruptive market shifts? They’ve survived them. Been there. 

    Painful organizational restructuring? Done that. These candidates don’t just have longer resumes; they have battle-tested judgment formed through success and failure alike. During crisis moments, which are the norm, they won’t be experiencing corporate trauma for the first time. While others panic, they’ll draw from their deep well of experience, providing stability when your team needs it most. Build a team of octo-shaped contributors and you’ll lower your risk of failure at least 8-fold.

    3. Organic mentorship

    Senior professionals naturally mentor those around them with humility and respect. I’ve watched it happen. One experienced hire can elevate an entire team through day-to-day interactions; this organic knowledge transfer happens naturally. It emerges during code reviews, strategy discussions, and impromptu conversations. These moments shape your company culture.

    4. Adaptability in the AI era

    As AI tools evolve exponentially, I’ve noticed a pattern: professionals with diverse experience adapt faster. Their mental models extend beyond a single domain; they quickly grasp emerging technologies and how to apply them to capitalize on business opportunities.

    Think of it like this: AI gives us superpowers by filling in our skills and experience gaps. The developer can instantly craft product documentation; the designers can instantly code. Now imagine how quickly someone with experience spanning eight disciplines adapts and how little AI has to fill in the gaps. Now imagine how fast this person will be at leveraging these superpower tools to drive your efforts further while bringing the team along with them.

    5. Proactive problem anticipation

    When you’ve seen enough projects struggle, you develop a sixth sense; you feel it in your gut as much as you see it in the data. Experienced professionals don’t just solve problems; they anticipate them, get in front and prevent them. This foresight saves valuable time and resources that would otherwise be wasted on firefighting.

    6. Day-one impact

    While less experienced hires climb the learning curve, seasoned professionals create immediate value. They hit the ground running. They bring tested methodologies, frameworks, and approaches refined through years of implementation; this accelerates progress and drives faster returns on your investment. 

    7. Connecting tactics to strategy

    Experienced candidates understand the relationship between daily operational work and long-term strategic objectives. They see the bigger picture and have spent their entire career learning how to build their daily activities toward the end goals. In other words, they unconsciously make decisions with immediate needs and strategic goals in focus. The insight is invaluable because it keeps the entire process on track and moving forward as if you automated it with AI.

    8. Crisis navigation expertise

    Your company needs steady leadership during uncertainty, which experienced professionals deliver. They’ve weathered market fluctuations that sent others into panic mode and guided teams through difficult challenges without losing morale. 

    When unexpected challenges arise—which we all know is the norm—these veterans maintain composure under pressure, because they’ve seen it before. They automatically deploy recovery strategies that they’ve learned through trial and error. They know when to pivot and hold firm while keeping everyone on the same page.

    9. Extensive professional networks

    Every experienced hire brings their professional ecosystem with them. Think about that value. Their network can provide access to specialized talent, partnership opportunities, and industry insights; these connections become an extended resource for your organization. Networks compound advantage.

    10. Self-directed performance

    Most valuable: experienced professionals work autonomously. They need minimal direction. They set appropriate goals, communicate effectively, and deliver consistently without requiring constant oversight; this independence is increasingly crucial in today’s distributed work environment.

    So the next time a resume with “too much” experience crosses your desk, consider reframing the situation. What appears as overqualification to the old you is seen as an opportunity to the new you. You’ll see that this is exactly what your team needs to thrive and grow. Deep, varied experience isn’t just valuable—it’s becoming increasingly essential for navigating today’s rapidly evolving business challenges.

    Image generated with the help of ChatGPT by OpenAI.

  • Vertical knowledge is acquired; horizontal excellence is accumulated.

    Vertical knowledge is acquired; horizontal excellence is accumulated.

    TL;DR: Industry knowledge can be learned quickly, but the ability to ship successful products takes years of experience across multiple domains. The best PMs bring battle-tested expertise that adapts to any vertical, making diverse experience an advantage, not a limitation.

    In product management, there’s a myth that industry experience trumps all. But after years of watching PMs transition between sectors, I’ve observed something crucial: the best ones don’t start from scratch—they bring their entire playbook, ready to adapt it to new challenges.

    Learning a new vertical’s language takes weeks. Understanding its unique challenges takes months. But knowing how to ship complex software? That takes years of accumulated battle scars and a proven track record of delivering results.

    Workflows vary by context, but the core principles of shipping successful software remain consistent. So no matter what you’re building, the fundamentals remain constant: deeply understanding user needs, championing stakeholder priorities, prioritizing for maximum impact, and—most critically—delivering on-time results.

    Great product managers aren’t defined by the verticals they’ve worked in, but by the horizontal expertise they’ve built across every launch, every pivot, and every hard-won success. In fact, diverse vertical experience may be more valuable than narrow specialization because it proves you can adapt your expertise to every new challenge.

    My journey reinforces this truth. I began building CMS-powered websites, then navigated through commercial financial services, marketing platforms, and enterprise social collaboration systems that united thousands of users. Each vertical demanded new vocabulary and developing domain expertise, but the principles of shipping great software remained constant.

    When I moved into idea management—helping organizations identify patentable innovations and transform their culture—I realized that whether you’re routing breakthrough ideas or managing any workflow, excellence comes from accumulated experience, not acquired knowledge.

    You can always teach someone your industry or niche. You can’t teach people decades of shipping excellence. As a lifelong learner, I’m excited to take on the next challenge.

    Visual concept developed in collaboration with ChatGPT and DALL·E by OpenAI.

  • Employee Ideation: Three Different Approaches

    Employee Ideation: Three Different Approaches

    TL;DR: Over nine years, I’ve implemented three idea management approaches: Social platforms worked when leaders engaged; targeted innovation challenges delivered the best results with the least overhead; and traditional suggestion boxes gave everyone a voice but were resource-intensive. Based on my experience, I recommend starting with targeted innovation challenges.

    I’ve spent the last nine years implementing different employee idea management programs; some approaches work better than others. Here’s what I’ve learned from running three distinct models across an organization of 250,000+ employees.

    The Social Bubble-up Approach

    The first program was an open ideation platform where employees could post ideas for everyone to see. Others could comment, vote, and collaborate. Popular ideas naturally gained traction and caught leadership’s attention, aided by community managers who informed executives about trending ideas.

    When leadership was engaged, this bubble-up approach worked well. Ideas improved through collaboration, departmental silos dissolved, and innovation became an ongoing conversation instead of a quarterly exercise. I still remember how a casual comment from a legal partner transformed a product manager’s idea into a patent. That kind of cross-pollination wouldn’t have happened otherwise.

    But the failures were just as instructive. Employee enthusiasm crashed quickly in groups where leaders didn’t prioritize reviewing ideas. Nothing kills creative participation faster than seeing your ideas vanish into the digital void. 

    Flipping the Script: Targeted Innovation Challenges

    After mixed results with the open platform, we tried something completely different after serious market research, pilots, and testing. Instead of asking for random ideas, we had business leaders identify specific business problems they needed solved, which reversed the typical ideation flow in a way that fundamentally changed the dynamics.

    We would hold time-boxed events, and the process was straightforward:

    • Week 1: Problem statement presented to the team
    • Week 2: Team members submit their solutions (both as teams or individuals)
    • Week 3: All participants reviewed solutions and voted; the best ideas rose to the top
    • Week 4: Leadership selected and implemented the best solutions, and the whole team was celebrated by leadership

    This approach connected employee creativity directly to business priorities—and the results were remarkable. What impressed me most was that even people whose ideas weren’t selected reported positive experiences. The transparency throughout the process—seeing exactly why certain solutions advanced while others didn’t—kept everyone engaged.

    The downside? Creative ideas outside the defined challenges went nowhere. Some brilliant but poorly presented solutions lost to lesser but better communicated proposals. Coordinating these events required leadership buy-in and support, which would become easier as the success stories spread through the organization.

    The bottom line was that this approach consistently delivered tangible results. Leadership got implementable solutions that solved real problems, and employees felt valued for their problem-solving abilities. It was a win-win.

    Traditional Suggestion Box

    Then, the company leadership changed, and we were asked to build what I would describe as a traditional suggestion box. Employees submitted ideas privately, which a central team read and routed to appropriate department-specific teams and then to their organization’s decision makers. We built tracking systems to communicate the implementation status back to submitters.

    Benefits: 

    1. Everyone had a voice—By providing a central place to share ideas, you give everyone a voice, which initially feels like a big win.
    2. Leadership support—For this approach to work, you must have the support of the company’s leadership. Luckily, we had that support, which elevated visibility, support, and adoption. 
    3. Cultural change—When the entire company is shown the value of reviewing and responding to employee ideas, it changes how everyone thinks about the organization and their work in a positive direction.

    Challenges:

    1. Expensive to staff at scale—The bigger the company, the bigger the team you’ll need to review, route, decision, and implement ideas. 
    2. Additional workload—Decision makers from every business line had to be trained and encouraged to participate in and review ideas relevant to their subject matter expertise. These leaders already had much to do, so accepting this new responsibility was mixed as you might imagine.
    3. Complex Processing—Manually reviewing and routing every idea was an imperfect process. The complexity of ideas often meant they needed review by multiple business lines and decision-makers, which added complexity to the routing, decisioning, and implementation of ideas.
    4. Meeting Expectations—The biggest challenge, a real human challenge, was that no matter how the idea was handled, meeting the submitter’s expectations was nearly impossible. 
    5. Avoid becoming a dumping ground—The last challenge is to prevent your suggestion box from becoming a dumping ground for complaints or transforming into a support desk. 

    My Recommendation

    If you’re considering implementing an idea management program in your organization, save yourself some pain and start with targeted innovation challenges. They deliver the best balance of employee engagement and business impact with the least administrative overhead. Find an AI-powered SaaS solution that best matches your organization and then experiment with a small group before expanding to the entire company. Also, be sure to provide a distinctly separate place for employees to get support and submit complaints.

    Social platforms can work for idea generation but are not great for idea management. They’re better for other employee engagement activities and collaboration. If you go this route, spend more time and energy on automating employee listening to discover ideas and a separate app for managing their implementation. 

    A suggestion box would work well for a small company, but I wouldn’t take this approach at scale unless you did five things from the beginning:

    1. Make meeting employee expectations your top priority
    2. Obtain executive support across the company
    3. Build automated idea review and routing using AI
    4. Build an AI assistant to help lighten the load on decision-makers
    5. Connect it to your current issue-tracking system(s) to streamline implementation

    Ultimately, meeting employee expectations is very hard. Ironically, the most important trait of a good product—user acceptance—is also the biggest challenge for this idea management approach.

    If you give a user a feature, it must work. If it doesn’t work, people won’t use your product. So, if your approach is flawed and doesn’t meet user expectations, don’t build it; choose another approach and try again.

    Have you tried any of these approaches in your organization? I would like to know which aspects resonated with your experience and what other methods you’ve found effective. 

  • What Separates Companies Widening the AI Gap From Those Watching It Grow

    What Separates Companies Widening the AI Gap From Those Watching It Grow

    TL;DR

    Companies and individuals adopting AI tools are seeing measurable productivity gains. Those who delay face a widening capability gap as the technology matures.

    For Companies

    1. Deploy LLM Tools Internally

    Implement AI tools for internal use across your organization to increase productivity across departments, from marketing to customer service to product development. Teams can automate routine tasks, generate content faster, and analyze data more efficiently.

    By implementing a phased rollout, you can:

    • Address security concerns methodically
    • Train employees effectively (leveraging how LLMs can teach optimal interaction methods)
    • Identify high-value use cases before scaling

    2. Customize AI for Your Business

    Train LLMs on your business using reinforcement learning from human feedback (RLHF). Even smaller companies can now fine-tune existing models on domain-specific data with reasonable resources.

    The more your AI understands your business specifics—products, customers, processes, terminology, and historical context—the more useful it becomes. A customized LLM becomes a competitive advantage as it embodies your institutional knowledge and can make decisions aligned with your company’s unique approach.

    3. Hire Versatile Talent

    Begin hiring T-shaped and Pi-shaped people instead of specialists for:

    • Product development and innovation
    • Customer experience
    • Marketing
    • Operations
    • Strategic planning

    Generalists better navigate technological transitions because they’ve already bridged specialists’ skills gaps. AI tools more effectively fill those remaining gaps. These versatile professionals adapt quickly to changing landscapes and apply AI across multiple domains.

    For Individuals

    1. Master the Right Tools

    Learn these tools outside of work:

    • Claude: For generating and refining writing, long-form content, and structured code with clarity
    • Perplexity: For research, fact-checking, and retrieving up-to-date information
    • Replit: For building and testing prototypes, especially for coding projects
    • ChatGPT: For brainstorming, refining ideas, summarizing topics, generating structured plans, and creating custom images
    • ChatPRD: For creating detailed product requirement documents and specifications
    • Grammarly: For editing, grammar checks, AI detection, and plagiarism prevention

    2. Build a Forward-Thinking Network

    Connect with people who are already embracing AI in your professional field. Not everyone around you will adapt simultaneously, so seek out those ahead of the curve. 

    These connections can provide valuable mentorship opportunities, collaborative partnerships for skill sharing, insights into practical applications, exposure to diverse use cases across industries, and early access to emerging techniques and tools before they become mainstream.

    3. Navigate with Strategic Vigilance

    Adjust your career path to anticipate technological shifts. You don’t need constant vigilance to spot important trends—just deliberate observation at key moments.

    By periodically assessing the technological landscape, you can:

    • Identify which skills to develop next
    • Choose projects that showcase your adaptability to AI-augmented workflows
    • Target industries positioned to thrive rather than merely survive

    Conclusion

    AI is already reshaping workflows across most professional fields. Whether you lead a company or navigate your career, the principles remain the same: embrace available tools, customize them to your specific context, and build versatile skills that complement rather than compete with AI capabilities.

    *(paragraph deleted)*

    Image generated with the help of AI (ChatGPT & DALL·E).

  • 10 Best Practices for Exceptional Product Management

    10 Best Practices for Exceptional Product Management

    Many articles about product management read like they were written by someone who read about it in a textbook. They talk about frameworks and methodologies as if following a recipe will magically result in success. But after years spent building products, I’ve learned that the difference between good and exceptional product management rarely comes down to which agile methodology you use.

    Product management is about people. It’s about getting designers, engineers, and stakeholders to believe in a vision that doesn’t exist yet. It’s about building trust with your users, even when you’re still figuring things out yourself. Most importantly, it’s about creating an environment where great ideas can come from anyone—not just the person with “Product Manager” in their title.

    I’ve made many mistakes and learned from them all along the way. These ten practices have consistently helped me turn scattered ideas into shipping products. They’re not rules set in stone—they’re hard-won lessons that might help you navigate your product journey.

    1. Own Your Vision while Keeping It Real

    I learned this one the hard way: without a clear vision, your product becomes a bunch of features in search of a purpose. But here’s the thing – your vision doesn’t need to sound like it belongs in a TED talk. It just needs to click with your team and make them think, “Yeah, I want to help build that.” When I was launching our idea management platform, our vision was simple: “Help employees get their ideas in front of people that can turn them into reality” That clarity kept us focused when tempted to add every feature.

    2. Build Prototypes

    Stop writing documents and start building. The best meetings I’ve ever had started with, “I know I’m stepping outside my role, but let me show you what I threw together last night.” Your prototype may be rough, but that’s okay. It gives people something real to react to, and you’d be amazed how a basic wireframe can spark better conversations than a 20-page spec. After all, TL;DR is a real thing.

    3. Stand Your Ground, pivot when needed

    You need conviction to overcome doubt. Many said users wouldn’t want certain features when developing our innovation event app. But our research showed otherwise, so we stuck to our guns—and those features ended up being key differentiators. Remember: there’s a fine line between conviction and stubbornness. Listen to feedback, especially when it’s coming from multiple directions.

    4. Build Your Dream Team through leadership

    Product managers didn’t build the best products I’ve worked on – they were built by diverse teams who weren’t afraid to challenge each other. Get your engineers involved early in product decisions. Have your designers shadow customer calls. Let your researchers poke holes in your assumptions. Magic happens when people step outside their usual lanes and share ideas.

    5. Show, don’t tell

    PowerPoint is where good ideas die. Want to get buy-in? Build something people can touch, click, or play with. When I have something complicated to explain, I draw pictures instead of using my words, or if needed, I build a prototype. It’s a cliche, but pictures are worth a thousand words.

    6. Create Buzz

    Products need momentum. Find ways to make your project the thing everyone’s talking about. Run internal demos where engineers can show off their work. Host lunch with stakeholders and get people excited to be part of the journey.

    7. You are Your Users’ Best Friend

    Get obsessed with your users. I block off “research time” every week—sometimes, it’s formal user interviews, and sometimes, it’s directly participating in customer support. I’ve spent tons of time watching people work—like virtual ethnography—to spot unmet needs better. The insights from those conversations have helped me identify the most successful improvements.

    8. Find your way to saying YES

    Product managers are often taught that their job is to learn to say no. That’s wild, but I get why they think that’s necessary. Change your thinking to turn that urge into a drive to say yes. There’s a reason behind every ask. Dig deep and find the root cause, then chart a path to the right solution.

    9. Lead Inclusive Meetings

    Nothing kills innovation faster than meetings where two people dominate while everyone else multitasks. I start product discussions with quick round-robin input from everyone in the room. Sometimes, the best ideas come from the quietest people—if you give them space to speak up. In no time, the introverts may even turn into your biggest contributors.

    10. Cut the bull

    Be straight with your team. If something’s not working, say so. If you don’t know something, admit it. If you need help, ask for it. Trust me, people can smell corporate speak a mile away. The real talk builds real trust.

    The Bottom Line

    After years of shipping products, I’ve learned that the best PMs don’t have the fanciest frameworks or the biggest product specs. They’re the ones who can take a simple idea and turn it into something people want to build—and use.

    I’ve seen brilliant product ideas die because their champions couldn’t bring others along. And I’ve seen seemingly modest ideas turn into game-changers because their PMs knew how to rally their teams, navigate the chaos, and keep pushing forward when things got tough.

    Exceptional product management isn’t about being the smartest person in the room. It’s about being the person who can bring out the best in everyone else. You won’t always have all the answers—you need to ask the right questions, spark the right conversations, and create an environment where great ideas can flourish.

    So take these practices and make them your own. Adapt them. Break them when you need to. Remember: your product’s success depends less on your process and more on the people you bring together and inspire. Now, build something that matters.

    Image generated with the help of AI (ChatGPT & DALL·E).

Privacy Policy - Terms and Conditions