Implementing feedback into our work culture

Healthy organizations are places in which feedback is encouraged, even if it’s about issues that are not easy to hear. How does this work?

Source: Implementing feedback into our work culture

Curated links for Product Managers

everything.pm is a curated page with resources for Product Managers

Product Management Predictions

Product Management Predictions: With January already over, it’s a bit late for annual forecasts. But then again, looking into the future is a secret superpower every Product Manager should look to develop. Therefore, it’s never too late to have an understanding of what comes up next. Mason Adair of Digital Product People did so for the profession itself.

Product Management Predictions for 2020

Ten Wild Predictions, One True Story and some Solid Career Advice

From the article

Just like the industry is changing. And the article makes an effort to put into relation the different aspects Product Management has. Mason starts his thoughts by looking into public available metrics that indicate the importance and projected relevance related to management of products. In this analysis, related topics range from Agile, Minimum Viable Product, Design Thinking, Lean Startup, Product Market Fit, Rice Prioritisation and Net Promoter Score all the way to Jira, Trello and Asana. With an analysis of how relevance for these topics changed over time, the article goes into setting the scenes for professional trends that influenced the past years. These include economic environment, the introduction of new technology, a demographic shift, increasing societal fragmentation and climatic change.

Product Management Predictions shape the conclusion in his article: 10 wild predictions I believe are not that wild. The top most prediction, Product arriving at the C-Level, is almost no prediction anymore. Digital companies already have recognised the importance to actively influence direction towards customers.

Read more: The Future of Product Management in the 2020s – Mason Adair – Medium

City Streets

Draw all streets at once. Probably qualifies as generative art, which exists way too little in this blog. Even though the author has some roots in it.

Tech layoffs spread (a bit)

Are January layoffs just a few post-WeWork jitters? TechCrunch has found itself writing about layoffs at a few notable tech companies this week — and not just Softbank-backed ones. The focus is very much profits, as Alex Wilhelm summed up on Thursday, especially after the failed WeWork IPO and subsequent valuation and headcount decimation. We’ll […]

From the article

Source: Startups Weekly: Tech layoffs spread (a bit) | TechCrunch

The Y2038 Problem

The Y2038 problem is similar to the Y2K problem. We’re exactly in between both about now. Both are 18 years away, in either direction. While Y2K is over and was obvious to everyone, Y2038 is not.

The issue here relates to a representation of date and time in Unix systems, and is therefore sometimes referred to as Unix Y2K. The root is the convention to store date and time information as 32bit unsigned integer in such systems. This means, possible values are limited. Time-differences in seconds, starting from 01.Jan 1970 cannot span beyond 03:14:07 UTC on 19 January 2038.

The Y2038 Problem
Calendar

The Y2038 problem will make all calculations beyond this date impossible, until migrated to another representation. At the time being, this seems far away. However, the problem casts its shadows already. Industries, in particular financial markets, often rely on long term forecasts.

Governance issued treasury bonds come with with the longest maturity. Often twenty years, sometimes thirty years. Calculations for complex, long running financing models easily try to estimate returns 20 years and beyond into the future. This is already beyond the problematic date that Y2038 brings. The code to run these calculations is typically complex and stable. Sometimes, it is as old as from 1970. Back then, this date-representation Unix engineers introduced this approach. 32bit covered a long period. John Femellia has a thread, over at Twitter, telling a story about the upcoming issues today.

Team Product Ownership

Team Product Ownership is a desirable property for any scrum team. Age of Product shares a few thoughts on how to encourage teams to think about customers and the product more.

Learn how to encourage product ownership with an initial day-long product mindset workshop for your Scrum team — Age-of-Product.com. #Mindset #Productdesign #Productdiscovery

Source: Age of Product

Product Owner vs. Product Manager

Product Owner vs. Product Manager: Product Management is a challenging role and requires diverse skills. Large organisation often introduce a split between two similar, close roles – Product Ownership and Product Management. Both requires a large set of skills.

Jordan Bergtraum, The Product Mentor, a mentor at The Product Guy, leads a conversation on this split.

Source: The Product Guy.

Microsofts Patch Tuesday

Y’all install Microsoft Patch Tuesday patches within 24h, right? This time Krebs On Security has some rumours that make you want to really install these patches in time.

Update: Washington Post reports, the NSA warned Microsoft about it.

The North Star Playbook

The North Star

As a concept, the North Star principle gained a lot of attention in Product Management recently. Amplitude, a vendor of analytics tools, has a guideline to this concept. Their playbook walks product managers, those that want to enter the domain or even those just curious about methods and principles through the ideas. But also sets the scenes for potential applications by walking through exemplary goals to achieve with this approach.

Stapler - The North Star
Stapler (by James Bowe)
Picture unrelated.

The playbook comes in 7 chapters, starting by describing the ideas to apply with the North Star concept. Only after the introduction the playbook enters the practical application of the concept, and with a chapter on product metric checklist checklists, it emphasises the importance of metrics. With this it also stresses the importance of selecting the right metric and not to lose a product in vain. E.g. active users would be the wrong metric, given the goal that shall be achieved.

More practical guidelines come with the chapter on running workshops in part 3, and the chapter on defining the right guiding metrics. In between, the document also gives success stories: there are sections that talk through a successful implementation of North Star at Netflix. But also Amplitude is leveraging the methodology and shares their experience in a section.

The closing chapters dedicate to debugging the processes attached, implementing them and over time changing directions.

Takeaway

In all the recent hype around the method, the key take away is to simplify ideas for your organisation. The approach is supposed to make it easy for your teams to understand the direction the product is taking. And even more following this direction. For a product management, communicating ideas should be a core skill. This approach gives great tools in doing so.

The guide to discovering your product’s North Star to improve the way you manage and build products.

from the Amplitude Playbook

Source: AmplitudeThe North Star Playbook