Skip to main content

Posts

Showing posts from June, 2018

Before Making Moves Based On Today’s Bad, Chart How All The Dots Align to A Path

Tip: if you want to change jobs, roles, careers, think about what you want in the grander picture (“vision”), and why your current situation is not fulfilling that vision. Don’t focus only on why you’re not “happy”.
There are a lot of folks who are curious of new jobs, new companies, etc. They usually have the same reasons for wanting to leave. At least, for many of the folks I meet with who want to join a startup from a large company. The last several folks I’ve met with work at large enterprises. Each shared almost the same reasons for wanting to leave – they didn’t feel valued, and they wanted to work in a smaller company where their work mattered.
Except, companies (big or small, established or startup) are all different. They differ in their cultures. True many big companies come with much structure – multiple layers. Then again, so, too, could small companies have layers. Small companies can be directed by very strong founders who have sole discretion of direction and product.

Continuation of Product Prioritization: Diving Into Story Mapping

I’ve been diving into different product management – importance of roadmap and product prioritization and then a RICE framework for prioritization. Today, wanted to jump back in but look at story mapping. I haven’t done a story map before, but I’ll share what I’ve found reading up on several sites including Aha!, MANIFESTO, Agile Velocity, ThoughtWorks, and others.

The benefit of story mapping is its effectiveness as a visual tool to organize the development tasks and activities with goals – the stories a product/ service user traverses. It prioritizes for value and aligns the team on value and goals.
How to think of story mapping – my preferred route: There are two axes – from left to right, the goals a user accomplishes to achieve a greater goal (e.g. make a purchase, stream a video, other). From top to bottom, the prioritization of stories (activities/ tasks) organized into a release schedule.At the top level, you have the intermittent goals a user achieves. All tasks and activities…

A Framework for Product Prioritization: RICE

Back to talking about product! Last week, I talked about the importance of product prioritization and the product roadmap. I’ve also shared takeaways from Des Traynor of Intercom talk on product development. Specifically, how to drive adoption and engagement. Today, here’s a framework for product prioritization – RICE. Reach – How many customers or prospects would a feature/ development engage?Impact – What is the outcome/ results of a build? Would this drive engagement – feature/ user adoption? Drive revenue?Confidence – How likely would development have the effect on reach and impact?Effort – How many total man-hours/ weeks/ months would this development take? Remember to include hours for each resource across functions (i.e. product, front-end, back-end).Intercom suggests teams add bands of scores to quantify each factor as best as possible. For example, to understand the factor of Impact, scoring can follow: “3 for ‘massive impact’, 2 for ‘high’, 1 for ‘medium’, 0.5 for ‘low’, and…