Arc Browser offers features that are great for someone glued to their computer all the time, and as a bonus, they enhance my product demos.
We’ve hit a tipping point where rapid delivery of features is no longer sufficient for both the customer and the business.
In a previous role, I took any chance to better understand how my product could satisfy the needs of my market. A beta release provides that opportunity.
Makers and designers are often taken aback when clients push back on allocating funds for user research and testing. Here's a software team's point of view.
It's important that decision-makers understand how the highest-paid person in the office (HiPPO) can negatively affect customers and the product team.
Your team will be stronger for it if you can discuss the problems that do come up with a sense of grace and an eye for improvement rather than shame.
So you’re staring down a big product launch. Instead of watching your [unit] tests fail, how might you monitor the way your launch issues manifest?
If you need to quell your nerves, start by making your best assessment of the types of issues that could come up after the product launch.
A software product roadmap is a framework for aligning the expectations of key stakeholders, customers, and influencers about the product direction.
When time and budget are especially constrained, teams can still channel the customer’s voice into what they build through adopting a hypothesis mindset.
Adopting a hypothesis mindset on product teams can mitigate the risk of wasted money developing features that don’t get used.
Having a hypothesis mindset includes having someone on the product team spend a tremendous amount of time talking to and empathizing with the customer.