Delivering 100% of Something Beats 20% of Everything Every Time

Software companies, especially SaaS companies, are constantly adding new features to improve the usefulness of their products. They even invented a term to describe it: continuous delivery.

You most likely are a customer of a SaaS product, and you’ve experienced the good and the bad of continuous delivery. The good is the joy of finding the product has something new that makes it easier to use. The bad is the surprise that awaits you when you log in next and discover something familiar has changed, not in a good way. Continuous delivery is here to stay, and it’s permeating every physical product that relies on software.

Here is where the people who build software fail us. They deliver a little of something for everyone, and they miss the mark. Features lack function. Workflows don’t flow. It requires too many clicks to do things that seem simple to you. So, why does this happen?

It happens because development teams get caught between a rock and a hard place. They try to please internal audiences at the expense of customers. They rationalize that checking off boxes shows progress to satisfy the angry hoards demanding more features faster. It’s far easier to demonstrate progress than it is to push back and do the right thing.

A more effective mindset is to deliver 100% of something rather than 20% of everything. It means that features are complete from beginning to end. It doesn’t mean they are perfect or can do everything imaginable. It means they are thorough. A customer can do something they want to do without resorting to contortions to get it done.

Software development projects quickly get out of control when trying to build 20% of everything. It’s called scope creep, and it’s what kills many projects. There are so many moving parts to the project that the entire project is in jeopardy. Delivering 100% of something requires focus and discipline.

This same mindset applies to launching products or any go-to-market (GTM) planning. Do 100% of something, not 20% of everything. Otherwise, it dilutes the efforts of the entire launch effort. For example, if a key result of a launch is to increase customer adoption, focus 100% of launch planning efforts on customer adoption. Anything else is a distraction.

So, today, commit to delivering 100% of something, not 20% of everything.

More from Dave @ www.brainkraft.com/product-launch-blog

--

--

--

Technology executive, founder of BrainKraft

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

CoreData-NSSecureUnarchiveFromDataTransformerName

How to make Tech tutorials without a Screen Recorder

How to enable logging on any Android app

6 Ways a Zendesk ITSM Integration With your ITAM software Will Benefit Your Business

6 benefits of Zendesk ITSM integration with AssetSonar

Managing Your Reputation As A Web Developer

My GSoC Journey

Count the Number of Words in a Word Document Using Java

Investigating Your Server

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
David Keith Daniels

David Keith Daniels

Technology executive, founder of BrainKraft

More from Medium

How getting into a Product team helped me become a better Marketer

Thinking Out of the Product #10

Thinking Out of the Product #10

Pivoting careers, curiosity, and rabbit holes

Landing a Product Marketing Role: Interview Questions