Are You Doing Stuff or Creating Value?

You can put a bunch of stickies on the wall, create tons of JIRA tickets and commit code, but are you creating value? Is the work you’ve done helping solve a problem for your customers or helping to acquire new customers for your business?

Product leaders often come to us because their teams are doing lots of stuff but that stuff is not turning into features that customers love. Stickies, tickets and code are just stuff –  they’re activity, not value.

Value exists in the hands of our customers and stakeholders. It exists when we can learn, when customers can take action, and when we start to drive business objectives (revenue, adoption, retention).

We train all of our staff in the Product Mindset and one of its three core values is to Minimize Time to Value. We believe that features guided by learning and user input take precedence over research and hypothesis.

If your team is doing a lot but not creating value quickly and regularly here are five guidelines you can follow, along with questions you should ask.

1. Put something in their hands

Is it in Sketch app but not a prototype? Does it work on your machine and not in a staging or production environment? Can I interact with it? No? Then you haven’t delivered any value aside from warm fuzzies and performance art.

2. Solve for Today

Scale is a problem we want, but do we have that problem today? Is the feature you are proposing an optional, nice to have? Does anyone want it, much less do tens of thousands of people want it? Does your technology and process allow you to excel at change? If so, then we can solve the mother of all traffic storms when it is actually on the horizon, not in hopeful anticipation. The highest cost of any feature is not its initial development time, but the cost and impact on future development.

3. Put customers first and your ego second

Do you think you are solving a customer problem or do you know? We all have ideas and preferences for the products we build and how we build them, but has yours been validated? Customers don’t cheat at prioritization. If you prototype and test ideas with your customers, you’ll know what to build. Use their guidance to avoid chasing shiny objects and steel balloons.

4. Celebrate grumbling over missing features

When someone complains that you are missing a feature, is that really a bad thing? Would you prefer feedback or silence? Having users who care and are invested enough in product success should be celebrated. It means they used it, they want more and you know what to focus your efforts on.

5. Use the 30 Second Rule

Imagine you are standing on the stage Steve Jobs style and you are going to pitch your product in 30 seconds. If a feature isn’t something that is worth talking about on the stage, is it  worth building? Violating the :30 rule can often give the appearance of providing someone, somewhere value and worth. Unfortunately, no, this usually isn’t reflected in the product.

Doing stuff is easy, creating value is hard, and minimizing time to value is ninja level. It means we need to move forward without certainty, that our company trusts us when we say there will be another release, and we have to be willing to give up things we want. If we can do all of those things, we will get to market faster, learn faster, and have a better chance of building products that thrive in this competitive world.

Jessica Hall

Jessica Hall

Director, Product Consulting

Jessica Hall is the Director of Product Consulting at 3Pillar Global. Previously she built the UX team at CEB and led the creation of the Newseum’s interactive exhibits and websites. Her work has been recognized by the Web Marketing Association, American Association of Museums, The Webby Awards, Time, Graphic Design USA, Forbes, and The Washington Post. She holds a Masters in Design and Digital Media from the University of Edinburgh and a BA in Journalism from American University.

Derek Tiffany

Derek Tiffany

Technical Manager

Derek Tiffany is a Technical Lead at 3Pillar Global and the Head of our Windows 8 Competency Center. Derek is an experienced Software Engineer with expertise across multiple technologies, including Microsoft .NET and Java/J2EE frameworks. Derek has a track record of successfully delivering enterprise software and integration components and has deep knowledge in how to provide and consume interoperable Web Services (SOAP and REST) and object serialization (XML and JSON). Derek is currently focused on consuming cloud-based services from mobile devices. Clients with whom Derek has worked at 3Pillar include RETI, Carfax, and many more.

Leave a Reply

Related Posts

Embrace the Product Mindset Our first public Product Mindset Workshop was rife with interesting conversations and discussions. One common theme that emerged from these was a pret...
“Team Conflict: Four Ways to Deflate the Discord that’s Kill... Jessica Hall, Director of Product Consulting at 3Pillar Global, had an article titled “ Team Conflict: Four Ways to Deflate the Discord that’s Killing...
5 Key Takeaways from Our First Product Mindset Workshop Sometimes, an idea or method is so ingrained in your company culture, it can be easy to forget it's not really “the norm.” It’s the classic “can’t see...
Take 3, Scene 22: Minimizing Time to Value On this episode of Take 3, we dive into the concept of Minimizing Time to Value with Andy Zipfel and Paul Doman, two members of 3Pillar's Client Servi...
Raj Kumar Bharti at the Component Driven Development Using R... On June 29th, Raj Kumar Bharti spoke at Component Driven Development Using React.js at 3Pillar Global's office in Noida, India. Component Driven Dev...


Sign up today to receive our monthly product development tips newsletter.