Quality over Quantity

Quality over Quantity

A project manager asked me for some coaching yesterday, thought I’d share it with you.

What she wanted help on, is how to know when a new solution is ready for the customer, whether the Finance organization, a business we sell to, or Sarah buying on a mobile app. As we drive towards technology at speed, agile delivery, fast to market, it can create a dilemma. We don’t want to launch something that disappoints, but we can’t afford to be slow in bringing value – How to reconcile these things.

What I’ve seen with many projects, especially at the beginning, is a desire to gather every possible requirement, every feature, function, capability that could ever be wanted, in huge blueprinting documents. Then under pressure to actually deliver something, it’s all developed as quickly as possible, shortcuts, workarounds, compromises are made to get everything possible into the solution and close off every ask. Then it’s launched and nothing works properly, it’s too complicated, users hate the thing and are quickly heading off to competitors or back to Excel. Even worse, customers carry on using it, but ignore and never use 80% of the features that were built.

The approach I advised her is to strive for quality not quantity. Customers will far more appreciate a solution that does the core of what they need it to do, and does it exceptionally well, with no workarounds or compromises on that core capability, rather than something that does everything, but poorly.

Far better to produce a quality trumpet with a beautiful tone and balance, than the cacophony of a one man band. Get it right from the beginning, don’t create huge requirements lists then trim, figure out early what the basics needed are, build it with quality, build it in a way that ensures it’s modular and extendable, launch it, then listen to your customers, observe how they use it, and build on the solution from there.

If you like the tip, click ‘like’, if you want to let everyone know your thoughts ‘comment’, if you think it could be useful for others in your network click ‘share’


Richard Thompson

IS OPS Change Delivery Project Manager at Centrica

5 年

Good bite sized, easy to absorb pieces of advice :)

回复

要查看或添加评论,请登录

Steve Marston的更多文章

  • Agile success with a penguin called Wilbur

    Agile success with a penguin called Wilbur

    When I started working at Centrica six months ago, if you told me I would be doing something Agile with the eponymous…

    6 条评论
  • 6 Steps To Deepen Team Ownership

    6 Steps To Deepen Team Ownership

    I wanted to share a few thoughts on how to secure and deepen the ownership of objectives and outcomes within teams: 1…

    5 条评论
  • 3 Simple Steps To Address Conflict

    3 Simple Steps To Address Conflict

    Had a friend come to me last week, head in hands, needing a sounding board. He felt like the last few months, his…

    5 条评论
  • My Space-station broke

    My Space-station broke

    Did you see the spacestation story last week with a hole in the hull? I took a lesson from their response that I…

  • How to measure success

    How to measure success

    Talking with a CEO last week, he asked for my guidance on how he could keep his IT project portfolio on schedule and on…

  • Is your current strategy going to drive your revenue and market share?

    Is your current strategy going to drive your revenue and market share?

    5 条评论

社区洞察

其他会员也浏览了