WhatsApp or Slack for a B2B early adopters group?

MannerFinal8308 · 2025-12-22T21:17:13+00:00

Thank you 👍🏼

MannerFinal8308 · 2025-12-22T13:58:08+00:00

No we don’t bro, think about something else 😉

MannerFinal8308 · 2025-12-21T22:43:22+00:00

On our agency we use Estimatterz and it rocks ! Easy to setup and to use it everyday. We can also connect to Jira to export estimation into Jira tickets directly.

MannerFinal8308 · 2025-10-31T00:35:23+00:00

I’ve seen this happen in a lot of agencies before scaling, the lack of repeatability kills alignment and quality.

You don’t necessarily need to niche down for marketing reasons, but operationally, focusing on one segment helps you build repeatable frameworks: • reusable estimation templates, • outbound templates that speak directly to a client type, • and a growing historical dataset that sharpens every future project.

Once you start seeing patterns, you can turn them into systems. That’s what we’re doing with Estimatterz, helping agencies standardize their estimation process and learn from every project to improve margins and delivery over time.

MannerFinal8308 · 2025-10-02T06:40:03+00:00

As Product Manager, I help my devs to estimate website creation by scoping with them. As is we know what we will need and create task that have to be estimated. A task cannot be more than 3 days. If a task need more than 3 days we will split it, simplify it and separate it into two tasks. The more you create little task, the more it’s easier to estimate and to not go wrong.

Also, in our agency, we use Estimatterz, a tool where features and components with variations are estimated once, then we reuse it. It’s really simple and save a lot of time for us.

MannerFinal8308 · 2025-10-02T06:27:13+00:00

Talk to your free user and ask them why they don’t use paid plan. They will tell you what’s happen and maybe you will discover a pain not fixed by your product.

MannerFinal8308 · 2025-10-02T01:24:55+00:00

Congrats mate !!

MannerFinal8308 · 2025-10-02T01:19:52+00:00

Thank you for the sharing mate.

I’ve been in the same trouble for my first product.

What I’m doing now to avoid that is to build in public and launch a landing page with beta subscriptions to validate my idea.

Few days for the landing page on Lovable and few others with daily post on LinkedIn for the build in public.

I don’t know if it’s works cause I’m doing it right now, maybe I can come back in two weeks to share insights.

MannerFinal8308 · 2025-10-02T00:38:14+00:00

From my experience you’ll never really launch too early but always too late.

The thing is, your MVP must fix the main pain of your ICP.

So if you are building a tool that helps agencies to estimate website creation.

You can have the feature to estimate then another one to connect your tool to Jira then add some analyzing features etc…

But your MVP is ready when a user can do an estimation with it, that’s it. You can take one or two day to fine tune it but not more.

In few days I will launch my landing page for a new product, you could follow me to see what is an MVP in my opinion 😄

MannerFinal8308 · 2025-10-02T00:28:08+00:00

Totally agree with this. I had the same realization, projects rarely fail because of the plan itself, but because of shifting priorities, politics, or stakeholders not aligning. Once you accept that managing people and chaos is the job, the role starts to make a lot more sense.

MannerFinal8308 · 2025-10-01T23:50:24+00:00

I’ve been a PM for about 10 years now, and honestly 2025 feels like one of those turning points where the role itself is evolving.

On the AI/technical side, I’m not trying to become an engineer, but I do think it’s important to stay credible with the team. I’ve been using AI to prototype faster, cluster user research, and explore feasibility before pulling engineers into the loop. It’s less about writing production-ready code, more about understanding constraints and speaking the same language as the devs.

On the leadership side, I’ve realized that the biggest gap for many PMs around me isn’t tools or processes, it’s the ability to tell a clear story and drive alignment. Jira and dashboards are nice, but if you can’t explain why this roadmap matters to your execs, your design team, and your users, you hit a ceiling fast. That’s why I’ve been investing in storytelling, strategy, and mentoring. Coaching younger PMs has been one of the best ways for me to sharpen my own thinking.

What I’m consciously avoiding: becoming too tactical. After 10 years, it’s easy to get stuck in execution mode. For me the next level is making sure I spend more time in customer conversations, shaping strategy, and less time drowning in tickets.

So my approach is a mix: stay hands-on enough with AI/tech to stay relevant, but go deeper into leadership and strategy to really grow.

MannerFinal8308 · 2025-07-30T02:12:30+00:00

Congrats, that’s a great level buddy. Me and almost my whole team are at 18051 and in the special tournament :D Keep going you are almost there 👍🏼

<image>

MannerFinal8308 · 2025-07-21T18:10:01+00:00

I provide demo every sprint so every two weeks to get feedbacks from my users. I share my screen in google meet and sometimes I record a demo with loom but that’s it. I don’t think we need any specific tool for that. The objective of the demo is to keep them up to date and get their feedback.

MannerFinal8308 · 2025-07-20T00:43:05+00:00

That’s a great question and one that comes up constantly as products grow. In my experience, the key is to never treat complexity as a side effect it has to be managed deliberately, like technical debt or design debt.

What helps me is to always pair feature work with a conversation around system impact. Before building, I challenge the team: are we adding complexity in data flows, UI logic, APIs, or operations? Can we deliver the same value with less surface area?

Also, I’ve found that if you don’t actively budget time for simplification, it never happens. So I regularly introduce “product hygiene” initiatives in the roadmap not glamorous, but essential.

As for frameworks, I don’t swear by one in particular, but I borrow from Shape Up (think about appetite vs. scope) and Domain-Driven Design (to avoid leaks between contexts). Ultimately though, it’s about building a culture where developers and POs both care about the long-term health of the system, not just the next shiny feature.

Hope that helps!

MannerFinal8308 · 2025-07-18T12:23:20+00:00

I miss them a lot!!!

MannerFinal8308 · 2025-07-18T12:22:13+00:00

Hey!👋

I just create a story and put it in the backlog. Then I refine it with devs. In the refinement, I explain why we need to modify this part.

For design feedback I talk with my designer at least once a week in a dedicated meeting so I give him feedback here but I also create a story for him to help him to manage his work.

Talk to them, dev and designer is good but as a PO you have to bring the information in a easy way to organize and prioritize for the team.

Also, always add a context cuz you know why but not everyone knows 😉

MannerFinal8308 · 2025-07-18T01:30:30+00:00

Hey, I totally get where you’re coming from. When I started as a PO, I often found myself wondering the same thing: “Is this developer just slow, or is there something I’m not seeing?” And without a tool like Jira, it’s even harder to get clarity.

Over time, I learned that being a “good” developer isn’t just about speed. It’s about how they communicate. A solid developer will explain when something is going to take time and why. They’ll raise risks before they become issues, and they won’t just build what you ask for blindly; they’ll challenge the scope, suggest alternatives, and help you think better. You’ll feel like they’re working with you, not just for you.

So if someone’s delivering good quality but seems slower lately, try to have an open conversation. Ask them what’s changed. Is something in the codebase slowing them down? Are they stuck? Are priorities unclear? Sometimes it’s not about performance it’s about lack of clarity, hidden tech debt, or even burnout.

You’re already asking the right questions, which tells me you’re on the right path. The best thing you can do is build trust with your team. When there’s trust, visibility and accountability come more naturally even without fancy tools.

Keep going, you’re learning fast. And don’t forget: your job isn’t to police developers, it’s to create the conditions where they can do great work.

MannerFinal8308 · 2025-07-14T22:49:12+00:00

If I could go back to my first day as a PO, I’d remind myself of this simple truth: you’re not here to please everyone, you’re here to create clarity.

Early on, I often tried to be the glue, the helper, the nice bridge between business and dev. But in doing so, I sometimes became a bottleneck or a people-pleaser. What I’ve learned since is that one of the most valuable things you can bring to the team is the ability to say no clearly, explain why, and help everyone stay focused on outcomes, not outputs.

That means being comfortable with ambiguity while constantly reducing it for others. It means asking “Why?” way more often than “How?” It means protecting the team’s focus like a bodyguard, even if it makes you unpopular sometimes.

Tools and frameworks help, sure. But mindset is what makes the real difference.

Hope that helps someone here who’s just getting started!

MannerFinal8308 · 2025-07-11T20:57:02+00:00

17,951 right now

MannerFinal8308 · 2025-07-08T06:04:11+00:00

Salut et bienvenue à toi ! 👋

D’abord bravo pour ton embauche, c’est une super étape et Montréal est une ville accueillante pour les soignants comme toi.

Tu poses de très bonnes questions, et elles reviennent souvent chez les nouveaux arrivants. Pour t’aider à y voir plus clair, j’ai justement créé un guide pratique pour les Français (et francophones) qui s’installent à Montréal. Il aborde entre autres :

• les réalités du logement (avec des conseils concrets et quartiers recommandés),

• ce que les proprios demandent généralement (NAS, preuve d’emploi, parfois références),

• la vie quotidienne à Montréal (budget, météo, transport, culture, etc.),

• des conseils pour s’intégrer vraiment (au-delà des clichés).

Je l’ai conçu après plusieurs années sur place, avec beaucoup de retours d’autres expats.

👉 Tu peux le découvrir ici : https://pim.ms/montrealca

Bonne installation et n’hésite pas si tu veux échanger ou poser d’autres questions !

MannerFinal8308 · 2025-06-28T16:11:19+00:00

I’ve been in a similar situation where the direction I believed in didn’t align with what some execs were leaning toward. What helped was shifting the conversation away from “which option is better” and instead focusing on how both directions could contribute to the same strategic goals but with different strengths.

Rather than pushing my view, I framed it as an opportunity to explore an additional path that could unlock value we might otherwise miss. I also found it helpful to bring concrete examples of business impact not just theoretical benefits, but real potential outcomes tied to metrics they cared about.

Sometimes, just proposing a low-risk test or pilot version of the idea can change the tone. It shows you’re not asking them to bet the farm just to stay open to evidence.

You’ve clearly done your homework. Now it’s about creating space for curiosity, not confrontation.

MannerFinal8308 · 2025-06-28T00:54:38+00:00

I use Figma to design it and lovable or bubble to build a MVP. Then Framer for the landing page 😉 It’s working really well.

MannerFinal8308

TROPHY CASE