Manjeet Singh

Great Question. I focus on three key areas: continuous innovation, deep customer understanding, and strategic differentiation. Here's my approach: Continuous Innovation: Maintain a robust product roadmap with both short-term improvements and long-term visionary features. Allocate resources for R&D and experimentation with emerging technologies, and encouraging ideation from all levels in the teams (product, design, dev). How you allocate varies based on your product stage.. but try to carve ...Read More

Yes, AI is eating the "execution layer" of product management: writing PRDs, crunching data, building dashboards, even synthesizing customer feedback. But here's what it's actually doing: it's raising the floor, not lowering the ceiling. The PMs who thrive won't be the ones who fight this shift: they'll be the ones who redirect their energy toward the skills AI can't replicate: judgment under ambiguity, task for what good looks like, cross-functional influence, systems thinking, and the ability ...Read More

First, Evaluate how disruptive gen AI is to your business If I don’t do anything, can competitors with gen AI make me obsolete? Creative work: advertising, design, gaming, media, entertainment A lot of document processing: legal, insurance, HR If I don’t do anything, will I miss out opportunities to boost revenue? Customer support: chat, call centers Search & recommendation Productivity enhancement: automated note-taking, summarization, information aggregation If there are opportunities, wha ...Read More

Here is my simplified formula to protect the strategy:Product Strategy Protection = (Clear Communication + Sales Enablement + Data-Driven Decision Making + Collaboration) * Leadership AlignmentBreakdown: Clear Communication: Effectively conveying the product vision, target market, and value proposition to the sales team. Sales Enablement: Equipping the sales team with the necessary knowledge, skills, and tools to sell effectively to the target market. Data-Driven Decision Making: Using data to i ...Read More

This is a 3 parts question, so let me take it one by one:Balancing user requests with optimal design: This comes down to mastering the art of prioritization as a PM. Pick a framework. For design I prioritize user requests based on frequency, impact, and alignment with product vision Conducting usability testing to validate design decisions, and have two version of design. A North Star to show end to end journey (to excite customer and cross functional team) and a smaller version that team can ac ...Read More

Traditional long PRDs quickly get outdated and don’t capture how AI features evolve through fast prototyping and iteration. Teams need a live, connected source of truth across ideas, designs, and decisions. Lightweight PRD + Prototype first – replace big docs with short context + goals + prototype flow that shows end-to-end user value. What tools I use.. and it might change so I am open to try out new version as they become available: Claude / GPT-4 – write, refine prompts, and generate concepts ...Read More

In fast-moving AI product work, scope changes are normal. My governance balances speed and control so we can iterate without chaos. Here is my scope change formula Triage fast – classify (minor/major) and decide if it fits this cycle. Assess impact – check effect on time, cost, and key metrics. Re-prioritize – keep only what drives clear customer value. Timebox – run small experiments instead of full rebuilds. Communicate + trade off – clearly state what’s in, what’s out, and why. For example: " ...Read More

I typically use a multi-tiered reporting approach: Weekly: Brief updates to immediate team and key stakeholders Format: Short email or Slack update Content: High-level progress, blockers, and wins Bi-weekly: More detailed report to cross functional leads Format: Presentation or detailed dashboard Content: Deep dive into metrics, progress on key initiatives Monthly: Comprehensive report to executive leadership Format: Formal presentation with Q&A session Content: All key areas, with emphasis ...Read More

The products I admire most are the ones that don't just solve a problem — they fundamentally redefine how you work and make you question why you ever did it the old way. As of this month, Claude Code does exactly that, and a few others come close.It thinks like an engineer, not a chatbot. it reads your entire codebase, debugs, runs tests, and iterates autonomously like a real teammate, not just a snippet generator. Terminal-native design is pure product taste. they met engineers exactly where th ...Read More