In my view, meeting-heavy processes totally detract the ability to have people in different time zones working together. Meetings also get in the way of deep work, which is needed in teams of builders such as Software Engineers, Designers, etc. Shopify recently banned meetings with 2 or more people for this exact reason.
With ad-funded models increasingly looking like a risky strategic decision for some product verticals at least, consumers have shown more willingness to pay for digital products and services they feel are valuable enough to do so. And with that, let’s take a look at some alternative business models you might want to explore.
In order to allow users of your product to manage the people who use it you’ll need to build some form of permissions system. But building permissions sounds a lot easier than it is.
When you’re building products using webhooks, your engineers can write code which allows you to ‘subscribe’ to a specific event and also specify the location for receiving the event. This process of subscribing and waiting for something to happen is sometimes referred to as ‘listening’ for an event. If you ever hear your engineering team refer to this, you’ll now know what they mean.
The tasks in a usability test should be realistic activities that the user might perform in real life when they’re using your product. They can be very specific or very open-ended, depending on the research questions and the type of usability testing.
One of the first introductions product manager might get into the world of architectural design is the concept of microservices. But what exactly are they?
As a product team, you have specialized needs that can be solved by NLP systems. For example, how do you offer your customers a customized search engine, in which they can quickly search items in your inventory? How do you build a chatbot that is just as smart as Siri, but can answer questions related to your own Customer Support needs?
With product management often requiring a diverse bunch of different skill sets, it can be overwhelming to try to structure your day in a way that optimises each of the activities these skill sets are used for. What’s the best way to manage the tasks a PM might typically be required to do in a day? Let’s find out.
What are the alternatives to scrum and kanban you ask? Here’s 3 different product development processes that modern product teams are using that you may very well have never heard of.
Product principles are used by product teams to help guide decision making. They may initially feel like a nebulous corporate waste of time, but once you’ve invested some time in developing them, you’ll rarely wish you didn’t.
Product strategy isn’t simply about clear decision making; before you can even begin to make any decisions about the direction of your product, you need to spend some time in diagnostic mode where you try to build a big picture snapshot of the health of your product.
Product management is concerned with deciding what to build, for who and why. Product marketing is concerned with figuring out the most effective ways of telling potential customers about what’s been built.
Developers are, and always will be, a critical part of product development. Not just because engineers are the ones actually building the products we use, but also because getting the engineering community on board as evangelists for your product can make or break your success.
If you’ve ever had the joys of working in both an early stage startup and a large corporation, you’ll understand the difference between a company with an operating cadence of ‘run’ and a company with an operating cadence of ‘stay afloat before the quicksand of corporate bureaucratic sludge kills you’.
Why accessibility can no longer be treated as an afterthoughtAccessibility is the practice of improving the usability of your products for a broad audience. When product teams hear the word “accessibility” they may think first of people with physical conditions: low...
Why an understanding of how your product is positioned is criticalA key responsibility for Product Managers is to define how their products are positioned in the market. Pricing, user experience, features, performance, branding, customer service and partnerships...
Ultimately, you’ll never know if what you’re going to build will succeed until you’ve built it. But there are some sensible steps to take before committing to building your product that will help you to increase its likelihood of success – and de-risk your likelihood of failure.
As a Product Manager, it can be difficult to justify your own existence. Luckily, earning respect from your peers can be a powerful way to fight off these feelings and misconceptions.
If your company’s success depends on growing effectively, you need to get these things rightWhen a company grows quickly, it undergoes stress. The faster the growth, the more the stress. Structure can make the situation better, but only if it is designed correctly for...
Realising the power of the product management tech lead partnership The composition of any product team will typically include a blend of: Software engineers UX / product design Product management The team may also include a UX content writer, a user researcher or...