ProductFTW #26: Driving Engagement
Identifying Specific Problems Leads to Targeted and Successful Solutions
Matthew Goldman
ProductFTW #25: User Problems
I see product managers attempting to mangle the problem into a problem that matters to them and that they can solve.
ProductFTW#23: Opinionated Product
The balance between customer requests and your vision
ProductFTW #21: Tips for Terrific Tickets
Every ticket, regardless of type (e.g., bug report, user story, compliance task), should contain a good title, description, impact, prioritization, and due date.
ProductFTW #20: The Challenges of Context Shifts
ProductFTW is about the skills and challenges of building software products. We can learn a lot from other types of work. A lesson from my mechanic inspired today's post about how PMs manage workloads and development cycles for their development teams.
A few years ago, my mechanic told
ProductFTW #17: For Whom Are You Building
I love upgrading my software. As someone building software professionally, I am eager to see what everyone else is working on. My eagerness to upgrade is often to my detriment, as early versions often contain bugs or some major change by the developer that isn’t to my liking.
Last
ProductFTW #14: Presentation Skills
One of the most effective ways to share critical information about a product or feature project is through presentations.
ProductFTW #9: Technical Debt, Features, and Time Management
A frequent point of debate between product managers and technology development teams focuses on the allocation of time between developing new features and maintaining existing products. Development time, particularly in startups, is a limited resource that depends heavily on team size and must be carefully managed and allocated. In this
ProductFTW #3: Startups vs. Big Companies
Many startups, typically with a single product, only require complex cross-team coordination once they experience substantial growth.
ProductFTW #2: The Tire Swing Cartoon
The start of building a successful product is to know what it is you need to build in the first place, and that starts with knowing what the customer needs, not what the customer wants.