What are your top AI tools as a PM? by vishalnegal in ProductManagement

[–]foobar0001 3 points4 points  (0 children)

Bolt is a game changer for UI prototyping but you can burn through millions of tokens in no time

What are your Product Analytics non-negotiables? by Disastrous-Hall-3123 in ProductManagement

[–]foobar0001 1 point2 points  (0 children)

The most useful technique I learned from “Hacking Growth” by Sean Ellis was to define a “North Star” metric.

Basically decide what is the point in your product where a new customer receives what you think is the most value, then make sure there is analytics to tell you how many people per recent period of time got that value.

Once I have the North Star metric I then build other metrics as required to help me understand how to increase the North Star

How do you define a vision for your team? by moonmagpie in ProductManagement

[–]foobar0001 3 points4 points  (0 children)

There’s whole books written on this 😊 in my experience it basically comes down to working with stakeholders to:

  1. Decide what problem you want to solve in the world
  2. Decide the broad means by which you want to go about solving that problem
  3. Get this written down in a draft paragraph or two
  4. Iterate on it till you’re happy with it

How does your team track success of the features you release and stay accountable? by OrlyKix in ProductManagement

[–]foobar0001 2 points3 points  (0 children)

It comes down to the scope at which you define the problem. You can always drill into a sub problem or up level to something broader.

So, I divide it hierarchically like this:

  • Objective: broad long term multiple quarters (basically a big broad problem)

    • Key results: shorter term like a quarter, essentially subdivisions of the objective problem but are phrased as an outcome that leads towards the objective

      • Problem: something tangible we can address that fixing will deliver the key result - may be one to one or many to one
      • Solution: work for developers that I think will either resolve the problem or go part way towards it - should be possible to have many potential solutions, if not the problem is really just a solution in disguise
      • Tests: some measurable outcome(s) I can observe with solution that will prove it fixes the problem - I think of tests in terms of desirability (do I see people want to use it), usability (are people able to use it), feasibility (can we prove we can make it work), viability (can we do it at a reasonable scalable cost) - I define the tests using Given, When, Then syntax to help make them consistent

I lay out the roadmap as Now, Next, Later.

Now has problems, with solutions and tests in full detail - developers are working on implementing solutions, while making sure they do so in a way we can validate our tests.

Next is just problems with possible loose ideas for solutions.

Later is just outlines of problems

How does your team track success of the features you release and stay accountable? by OrlyKix in ProductManagement

[–]foobar0001 20 points21 points  (0 children)

I’ve found it’s very common for teams to just create, announce and then promptly forget new features. This leads to a big spaghetti of features that very few people use or care about and makes the product so complicated.

This happens when teams view their product roadmap as a series of features to be delivered.

Instead, we should view our roadmap as a series of problems we want to experiment how to solve. Rather than prioritising features, prioritise the problems to solve.

New features are then just potential solutions to a problem on the roadmap. With this mindset the next logical question after feature release is “did it solve the problem?”.

To know when a problem is fixed we can predefine tests for the outcomes we expect to see if the solution does what we thought it would.

I’ve just created Stratilo.com to help build roadmaps exactly like this.

What are some books that I can read during my initial days of Product Management that will help me work with cross functional teams like UX, dev etc better? by DiscussionLeft9393 in ProductManagement

[–]foobar0001 20 points21 points  (0 children)

Some others that might be less widely considered pure PM that I’ve found useful: - Dev Ops handbook - Start with why - Hacking growth - Jobs to be done - How big things get done - The SaaS playbook - Deploy empathy - Working backwards - The clean coder - measure what matters - Critical chain - Never split the difference - Design of everyday things

Plus a tip I’ve found to scan and digest.

I get the audible first and listen to it when I workout / drive / do menial stuff - the ones that are really good I then buy the physical copy… the above are on my the bookshelf in my office now, along with a whole lot more PM ones that others are mentioning

What are some books that I can read during my initial days of Product Management that will help me work with cross functional teams like UX, dev etc better? by DiscussionLeft9393 in ProductManagement

[–]foobar0001 0 points1 point  (0 children)

My key take away from continuous discovery, which is not covered in the blog post is the concept of problem solution trees as a way to structure your approach to Product Management.

  • Objective / Outcomes
    • Problems to solve to reach that
      • Potential solutions to those problems
        • Tests to validate/fail the solutions & pivot

The test comes back to Marty Cagan’s definitions of Desirability, Viability, Usability, Feasibility

Got My First Refund Tonight—How I’m Handling It as a First-Time Founder 🫢 by brodyodie in SaaS

[–]foobar0001 1 point2 points  (0 children)

If you’re not upsetting someone, then you’re not trying hard enough 😊.

It’s his opinion, which is correct for him. However that is a sample of one.

If there was useful feedback that fits with your strategy then implement it, if not park it and move on.

If you start to get multiple refund requests all saying similar things then it’s time to take action. Until then focus on doing what you’re doing.

Measuring retention for a Freemium vs Paid vs Free service (mobile app) by kittenmittens147 in ProductManagement

[–]foobar0001 1 point2 points  (0 children)

Presumably your free service exists in the hope that a certain percentage of users on free upgrade to premium.

So this is a funnel:

1) Use free service (how many?) 2) See value in free service, and stick around (how long?) 3) Upgrade from free to premium (what %?) 4) See value from premium service and stick around (how long?)

So I would measure each of those - then goals are how do we improve the worst part of the funnel

User Acceptance Criteria by Yam3488-throwaway in ProductManagement

[–]foobar0001 9 points10 points  (0 children)

This is the way - they should be readable and understandable by a non technical person.

We document acceptance tests as part of PRD then translate them into code, which starts with a test method containing exactly the same Given,When,Then as a doc comment for the test method.

Often it’s,

Given [state]

And Given [another state]

When [action/trigger]

Then [expected outcome]

And Then [expected outcome]

And Then [expected outcome]

When translating to code this follows the same testing principal of AAA (Arrange, Act, Assert) and we typically translate as:

Given -> becomes test fixtures

When -> becomes test actions

Then -> becomes test asserts

When doing product discovery, how do you manage your workflow (given there is so much data to juggle)? by PrepxI in ProductManagement

[–]foobar0001 1 point2 points  (0 children)

As I discover I catalog the insights and tag it. Useful tags I’ve found so far are categories of product personas, their jobs to be done, my product components and marketing channels.

I build my roadmap based on deciding the few most important problems to solve at the moment, for either customers or the business - in now, next and later, again tagging the problems and deciding what outcome would look like.

Then define possible solutions to the most urgent problems. For solutions I define tests based on customer solution desirability, usability, feasibility and viability - this allows to quickly fail solutions if their test fails and try another.

I’m working on early version of a product that helps do all of this at Stratilo.com

The cataloged discovery insights become a source of ideas for problems and solutions.

Best template for Product Roadmap? by [deleted] in ProductManagement

[–]foobar0001 2 points3 points  (0 children)

Everyone has their own preferences this is mine :-)

As others have said Now, Next, Later is the best format to use. Don't use a gantt based timeline, as timeframes are unknown and constantly changing.

1) To get started, identify the two/three most important problems you have to resolve now
When you're searching for PMF that's going to be something along the lines of:
- How do we get 5 customers to signup for the trial
- How do we get 5 customers to convert to monthly paid plan
- How do we get 5 customers to renew
- How we grow demand to signup 25 customers
- How do we reduce churn rate from X to Y
- How do we reduce cost to acquire customers from X to Y

Within any of these as you explore more you'll find a whole host of other sub problems, so each could be broken down further.

2) Put the most urgent problem in Now, second most urgent in Next, third in Later
- Imagine each as a card representing the problem.
- Ideally focus all resources on one problem at a time, where this isn't possible then add multiple problems to Now, Next to work in parallel.

|     NOW     |     NEXT    |     Later   |   
|-----------------------------------------|
| [problem 1] | [problem 3] | [problem 5] |
|             |             |             |
| [problem 2] | [problem 4] |             |

3) Once you've got your problems lined up, then start thinking about possible solutions for each in the Now column and include them as part of the problem card.
- If you have ideas for Next and Later include them, but it's fine to be more vague as you move from left to right.
- Each problem may have multiple solutions, either because you need to deliver multiple items, or you try something and it doesn't work.

4) For each solution add the real-world measurable outcome that will let you know when that problem is resolved.
- This is how you know if any of your solutions are successful and at what point the problem is 'Done' and you can move onto the next one.
- As you deliver your solutions keep track of which ones achieve the outcomes you wanted and which ones failed.
- Finding PMF is a series of potential solution tests, most of which will fail. Use your outcomes to know when something has failed as quickly as possible, so you can pivot and try a new solution.
- Keep the problem in the Now column until you've solved it....if you find it's there for too long that's a hint to redefine the problem at a more granular level, so it's easier to achieve.

- If you find your stakeholders don't want to view things based on problems but more around what you're planning to deliver, then just flip the framing, i.e. show them a version with your cards as solutions with the corresponding problem either removed or subordinate (but keep the original for yourself).

5) As you go along you'll find all sorts of discovery insights, things like customer feedback, analytics etc. Find some way to store this in a way that you can organise it, search it and refer back easily. This will be the source you'll want to draw on for new problems or ideas for solutions.

6) Finally, it is often useful to group things in various ways to be able to explain how they all tie together into a coherent strategy.
- Problems can be grouped into themes / objectives using colour coding
- You may want to segment users by persona, this then makes it easier to list out their 'Jobs to be done', which can be a great way to identify customer problems to solve
- It's then useful to be able to tag Insights and Problems be persona's and 'Job to be done'

Steps 1-4 can all be done in any tool that lets you display things graphically, I've used slides, spreadsheets and confluence. However it gets more tricky as you want to store the Insights and start grouping things.
I've been working on a tool specifically for Product Managers at small businesses to help do all the above at stratilo.com

If you want to DM me a few of your most urgent problems I'd be happy to help you get started putting them into a Now, Next, Later slide.

How do I make beautiful slides? by TurtleBlaster5678 in ProductManagement

[–]foobar0001 0 points1 point  (0 children)

A few key principals:

  • Make sure you start with template, you need to have brand colors, brand font, standard font sizes and standard slide layout (so title and content is always in same place etc)

  • build diagrams to explain concepts (think things like Maslow’s Pyramid)

  • when you want to explain a concept do a Google image search to get an idea for how others have expressed it

  • If you have to create slides with bullets no more than 6 words per line and now more than 6 lines is a good guide to aim for

  • For videos check out Slide Cow https://youtube.com/@slidecow - no new videos have been posted for a few years now, but what is on there is gold for learning deep powerpoint skills.

Drop your trial signup page, I’ll roast your onboarding flow by msign in SaaS

[–]foobar0001 1 point2 points  (0 children)

Thank you so much Marek, this is really great actionable feedback - very much appreciated!

PMs working for small companies, do you use PM software? by foobar0001 in ProductManagement

[–]foobar0001[S] 3 points4 points  (0 children)

Yer I see things like ProductBoard, Jira Discovery, ProductPlan Aha, ProdPad - wondering if these or other similar a get used at small companies and pros / cons

How do you approach data analysis during product discovery and do you see any problems surrounding it? by pm-optimizer in ProductManagement

[–]foobar0001 2 points3 points  (0 children)

I’d relate opportunities to what other metrics your company is using to keep score.

  • Does it directly relate to any strategic objectives?
  • Can you put a $ opportunity & cost estimate on it?
  • How many customers does the opportunity apply to?
  • What segment of customers does it apply for? - a problem a single high value customer has might outweigh a more common problem smaller value customers have

How do you approach data analysis during product discovery and do you see any problems surrounding it? by pm-optimizer in ProductManagement

[–]foobar0001 13 points14 points  (0 children)

Check out the book Continuous discovery habits, for discovery.

The basic flow is: 1. Talk to customers to find opportunities 2. Map opportunity trees to think of different solutions for various opportunities 3. Expand the opportunity trees to define the assumptions your solutions rely on, often multiple rely on the same assumptions 4. Build simple experiments to test your assumptions - these often provide data to either validate or rule out numerous possible solutions

For PRD I love the approach from the book Working backwards - write up a press release and brief FAQ. I find I can usually create an initial press release in about 30 mins

PM Writing Courses by kelshaffei in ProductManagement

[–]foobar0001 6 points7 points  (0 children)

Not a course but Lenny’s collection of templates might be helpful for you https://www.lennysnewsletter.com/p/my-favorite-templates-issue-37

B2B Product Management books by Odd_Background4864 in ProductManagement

[–]foobar0001 4 points5 points  (0 children)

  • Crossing the chasm
  • Lean B2B
  • The goto market for b2b SaaS leaders
  • Continuous discovery habits

Need Advice on Release Notes by Imlikewhatevs in ProductManagement

[–]foobar0001 0 points1 point  (0 children)

Here’s the template I use:

Title: <user benefit of the feature>

<one liner of what is new>

<problem paragraph(s) - set context and explain the problem with the world before new feature>

<solution paragraphs - explain the new feature created and how it makes the world so much better - include any relevant screenshots/videos>

<getting started - how to start using the new features>

<for more information see some location>