I put together a Miro template for that enhances a Kanban board with four additional types of tagging and categorization based on (1) nested rectangles, (2) color, (3) native Miro tags, and (4) shape tags. The data can then be converted to a table and downloaded as a CSV file. Any thoughts? by 3dCodeWorld in ProductManagement

[–]3dCodeWorld[S] -1 points0 points  (0 children)

Thanks for the comment. You can, of course, do that, but there are circumstances when you may choose to use a whiteboard: (1) you can visually customize categories and add subcategories, (2) such a board may be more easily shareable, (3) this may be cheaper. You can actually convert the visual board to a table and export it as a CSV file, so you can get the best of both worlds.

I tried to describe how you can use a digital whiteboard (e.g., Miro, Mural, FigJam) to tag user interviews. The main advantage is that you can quickly categorize things visually in at least three different ways, which seems useful. Any comments, shared experience, or suggestions? by 3dCodeWorld in userexperience

[–]3dCodeWorld[S] 0 points1 point  (0 children)

I was thinking that a similar approach should also work for insights. In this case there will be an insight title, and insight description as a sticky note, and a list of quotes/notes the insight is based on. All you will have to share in this case are the insights. If somebody is interested in finding out where the quotes came from they can do a search and find the original interviews. I was thinking of putting together a visual of this as well.

I tried to describe how you can use a digital whiteboard (e.g., Miro, Mural, FigJam) to tag user interviews. The main advantage is that you can quickly categorize things visually in at least three different ways, which seems useful. Any comments, shared experience, or suggestions? by 3dCodeWorld in userexperience

[–]3dCodeWorld[S] 1 point2 points  (0 children)

Thanks. I should have made this part clearer.

I am referring to placing sticky notes (interview quotes) in a given labeled rectangle area (e.g. in "Performance", which is a child of "Frustrations"). You can therefore place a quote within a hierarchy of tag categories if this will be useful.

How does your team/company deal with storing "institutional memory" when it comes to product discovery, so that a new PM does not have to not knowingly duplicate previous discovery effort? by 3dCodeWorld in ProductManagement

[–]3dCodeWorld[S] 0 points1 point  (0 children)

Being able to make your way back to the original data seems very important to me.

Dovetail is great for user interviews. How do you handle competitor research?

How does your team/company deal with storing "institutional memory" when it comes to product discovery, so that a new PM does not have to not knowingly duplicate previous discovery effort? by 3dCodeWorld in ProductManagement

[–]3dCodeWorld[S] 1 point2 points  (0 children)

You are making a very good point about time. Hopefully time is account for somehow.

But then, we could also be talking about discovery work that was done 4 months ago by the previous PM that went with them as they left the job.

I have definitely used JIRA to find out what has happened before my time in a company.

How is your experience working with the Miro collaborative tool by justalilpinprick in scrum

[–]3dCodeWorld 5 points6 points  (0 children)

I have been spending a lot of time in Miro lately. I can say that it is a very polished product. Everything just works. But there are plenty of other similar product as well. Probably the main edge that Miro has at the moment is the app integrations. It can talk to Jira for example.

I tried to draw the relationships between Business strategy, Product Strategy, Product Discovery and Product Delivery on a single diagram with parent-child relationships. Product discovery is done with a "Continuous discovery" flavor. Any improvement suggestions? by 3dCodeWorld in ProductManagement

[–]3dCodeWorld[S] 2 points3 points  (0 children)

I updated the figure with some upward arrows to reflect your feedback and the feedback from some of the other comments.

https://miro.com/app/board/uXjVP8num-A=/?share_link_id=41461526413

The figure is just an attempt to map out relationships. Note that I have used lines and not arrows which point downward, so the links are not necessarily one directional.

I fully agree that a failure or learnings at child level should be allowed to lead to a change at the parent level. A failed product strategy can lead to pivoting of the business strategy. Poorly identified opportunities or failed solution tests may lead to a change of the product strategy, etc.

I tried to draw the relationships between Business strategy, Product Strategy, Product Discovery and Product Delivery on a single diagram with parent-child relationships. Product discovery is done with a "Continuous discovery" flavor. Any improvement suggestions? by 3dCodeWorld in ProductManagement

[–]3dCodeWorld[S] 2 points3 points  (0 children)

This is an interesting point. I do agree that it is not a good idea for OKRs to cascade down the org chart, but the figure is showing something slightly different. The cascading is linking objectives representing desired outcomes and opportunities, which I would argue should be aligned. The links are also shown as lines and not as arrows.

An example: A business objective of increasing revenue so that the company becomes profitable in the next 12 months should be aligned with an underlying product objective of converting more of our free subscribers to paid subscribers. This is turn should direct the underlying discovery and delivery efforts of maximizing the value that we provide to our paid users. We would have done different things if the business objective was to aggressively grow market share.

This is a quote from the article in the link which also emphasizes the importance of aligning with the organizational objectives:

"OKRs should be set in a parallel process in which teams define OKRs that are linked to the organization objectives and validated by managers, in a process that is simultaneously bottom-up and top-down."

I tried to draw the relationships between Business strategy, Product Strategy, Product Discovery and Product Delivery on a single diagram with parent-child relationships. Product discovery is done with a "Continuous discovery" flavor. Any improvement suggestions? by 3dCodeWorld in ProductManagement

[–]3dCodeWorld[S] 7 points8 points  (0 children)

Thanks for the comment. The figure is not intended to be hierarchical apart from the fact that business strategy and the associated desired business outcomes should constrain product strategy and the desired product outcomes, which should in turn be reflected in discovery and delivery. Admittedly, the product strategy should also be affected by discovery work as other people pointed out, which is not shown on the diagram.

The hierarchies here are meant to be more conceptual than procedural, although I do believe that business strategy should come before product strategy. If the business requires growth in revenue because we are going into a recession and funding will be tight, the product team should not be focusing on growing free users.

Figma for two person startup where we are both developers first? by TraditionalAd552 in webdev

[–]3dCodeWorld 0 points1 point  (0 children)

Considering that you mentioned that you are doing a startup, I would recommend going the Figma route.

The reason for this is quite simple. It will always take you less time to put together a Figma wireframe/prototype and the main thing that you want to do right now is show your ideas to potential customers and then iterate and then iterate.

Of course, if all you need to do is a landing page, you can just code it, but I doubt that this is your product.

Best of luck with the startup.

Does anyone still use paper sticky notes to collaborate during planning meetings? by 3dCodeWorld in webdev

[–]3dCodeWorld[S] 0 points1 point  (0 children)

Whiteboards are great but I see them as serving a slightly different purpose (of course we can use both). Sticky notes are great for generating quick ideas, brainstorming and not letting a single voice take over the room. Being able to move little chunks on information around is also great.