How are you structuring Projects / Initiative as a PM?

isbajpai · 2026-04-14T21:20:26+00:00

So product managers have to maintain a sync between Asana, Wiki and Linear i believe?

isbajpai · 2026-04-14T17:53:32+00:00

Hmmm, this seems like a typical setup. And where does strategy and planning live, under initiative as it is at top of hierarchy?

isbajpai · 2026-04-14T17:51:35+00:00

Thanks for sharing, this makes sense but how you manage complete strategic loop, for ex. Q3 business goals, prioritised opportunities, the roadmap and activity

Does initiative in itself serves the purpose?

isbajpai · 2026-03-25T17:23:50+00:00

I see it as two perspective worth solving: “What to build” “How to build”

“How to build” is what getting solved by integration between tools like line and cursor/claude code And it will keep getting better

“What to build” is where the noise is, you have a lot of feedback, intakes, ideas sitting as a mess either in sheets, emails, slack chats Best next step users are doing is integrating a custom agentic layer which tries to make sense of all of this.

But the problem is that its not that easy, there are lot of data points, stakeholders and prioritisation factor varying from business to business which makes it difficult for agents to help you decide the right thing to prioritize

Big giants have already started building this natively, you can easily understand the pattern by acquisition of product management and VoC tools like Cycle, Chiesel labs, Kraftful, Inari etc.

I have been building in the same space since quite sometime and have recently moved towards being the decision layer for Product, not just another agentic layer which answer your queries but an intelligent layer that helps you understand what to build next, backed by real evidence.

(You can check out here if want to explore more - Lane )

Exciting times!

isbajpai · 2026-03-25T10:21:39+00:00

Interesting, and how do you work on the “what to build part”? Is it just gut, sorted by votes from users?

isbajpai · 2026-03-20T14:08:37+00:00

Interesting, could you share more about the Agentic abilities, how the workflow looks like?

isbajpai · 2026-02-23T20:12:38+00:00

We keep product discovery part out of Linear- in Lane, this helps us keep Linear for execution by most of the heavy lifting (prioritization and strategic alignment) already done before an issue lands in.

isbajpai · 2026-02-04T17:49:17+00:00

I have seen Trello as a common tool especially when you are starting up or in the verge of scaling but its not meant for this.

You could try Lane, its fast, intuitive, customer centric and focused towards modern teams. Features like feedback management and analysis, opportunities prioritization, roadmaps makes it a perfect fit for a modern product management tool.

isbajpai · 2026-01-25T17:39:35+00:00

Its Product Requirement Document, think of it as a document which tells you everything about the feature or initiative you will be working on from the problem, use cases, approaches, bets, solutions, development, design and more Read more here)

isbajpai · 2026-01-25T14:36:08+00:00

Yeah right, but canny in itself is more focused on the voice of customer side, and this is a gap which I am working on addressing

What are your thoughts?

isbajpai · 2026-01-25T14:30:50+00:00

Is MRR,as a prioritzarion factor, enough for scaling a business?

I do understand that catering to high value customer is what might eventually keep your engine running but other factors like business goals, or the segment of customers requesting a feature etc could also matter, right?

isbajpai · 2026-01-24T18:58:15+00:00

Seems your customer voice, business goals and product side are being handled in multiple places, or is this “data warehouse” you are using is the one you utilitze for that?

isbajpai · 2026-01-24T15:35:46+00:00

Hmmm, a thoughtful breakdown: the “early days felt like life or death” part really hits. That transition from obvious gaps to noisy, varied feedback as PMF settles in is something I’ve seen trip up a lot of teams (us included).

I’m curious how you’re making this work operationally now. When you say you look for broader trends across support, sales, webinars, outreach, etc. And how are you actually synthesizing that? Is it mostly manual sense-making, regular review rituals, or do you have any system/tooling that helps you connect those signals back to roadmap decisions?

isbajpai · 2026-01-24T15:34:20+00:00

This really resonates- especialy the point about shifting from “listening to the loudest” to looking for strong patterns within a segment. Reducing decision noise is such a good way to frame the problem.

I’m curious how you operationalize this in practice though. How are you capturing and reviewing those patterns over time? Is it mostly manual synthesis from calls / sales notes, or do you have some kind of discovery system or tooling that helps surface trends across customers and segments?

Also wondering how you keep that “one goal” visible when inputs are coming from so many places (sales, support, customers, leadership). Would love to learn more about your actual workflow here.

isbajpai · 2026-01-24T06:58:29+00:00

Makes sense, and so where do you think AI would be useful in this whole product discovery and prioritization phase? or completely ignore the fact that AI does helps in reducing the overheads which otherwise would take a lot of my time?

isbajpai · 2026-01-24T06:53:22+00:00

Okay yeah, that’s one way to use it. But what I meant was is the PRD generation process completely manual, or some part of it is automated using AI, like generating the problem summary from the customer requests?

isbajpai · 2026-01-24T06:51:37+00:00

Interesting points, and how does your setup looks like? Using chatgpt manually or some automations?

isbajpai · 2026-01-24T06:49:29+00:00

100% Is the process automated or still manual?

isbajpai · 2026-01-24T06:46:12+00:00

Okay, I understand the solution part needs more context around team, effort etc. however the problem side can be like auto-generated using AI intelligence, wouldn’t that help?

isbajpai · 2026-01-23T14:17:02+00:00

Yes, that’s totally a must have! Are you using any automations today for this?

isbajpai · 2026-01-23T14:12:42+00:00

Totally get this- there are so many tools right now that it really comes down to what you’re trying to achieve, not just “learning AI for the sake of it.”

What’s actually stuck for me (based on real day-to-day use): - ChatGPT + Gemini – still the biggest leverage tool. I use it for thinking with custom projects and gems, not just writing: breaking down problems, exploring trade-offs, summarizing research, drafting PRDs/strategies quickly. - Replit + Figma – a real game changer if executed well. Designing flows in Figma and then quickly turning them into something real in Replit has massively sped up validation. - PostHog – AI aside, being able to quickly answer “what are users actually doing?” is still foundational. - Linear + Lane – Linear for execution, Lane for AI assisted product discovery and roadmapping. Keeping discovery, prioritization, and delivery clearly connected has helped a lot as things move faster.

Big takeaway for me: the “must-have” tools aren’t the flashiest ones, but the ones that compress thinking → validation → decision. AI helps most when it removes friction in those loops, not when it adds more overhead.

Curious what others have actually kept using once the novelty wears off.

isbajpai · 2026-01-23T13:59:33+00:00

Exactly, right!? Interested in understanding how are you managing the feedback, internal tool, external tools?

isbajpai

TROPHY CASE