Skip to main content

Agile Programming and Agile Selling

In web tech, everyone is keen on Agile development.  If it's not agile (or a variant delivering similar results) most folks aren't interested.  The main themes behind Agile development tend to focus on speed, change, transparency and increased satisfaction.  Themes, in reality, can and perhaps should, be applied to most areas of customer facing business.

Everyone wants something yesterday.  Most people want improvements or changes to existing processes, standards or services.  Most people want to know what's going on  - and that is especially so when things go wrong.  So that means most people want transparency too.

One of the themes regarding agile design is that of feedback.  Good quality end user feedback is like the holy grail.  I don't mean good as in they like your stuff, I mean good as in it's quick, reliable and appropriate and can accelerate the development process with regards to identifying bugs, incorrect features or processes.

Selling should be the same.  A new market or product will not necessarily take the form of existing channels.  Understanding of the customer, their problems, the solution they require and how that should be packaged and communicated are key to any sales execution. 

How agile are you?

How is that done in practice?  Replication of existing practices is generally the normal starting point.  "If it's worked before it will work again..."  A decent thought process.  What is key, is the ability to learn quickly if that process works or fails.  That requires a metric to determine what is classified as successful, as well as a method to be able to collate and collect that metric - the feedback theme again.  How is that possible?  Metrics are all around.  Click through rates, response rates, conversion rates, attendance rates, signup rates, referrals, recommendations, cancellations.  The key is to understanding the numbers that are returned.  What is considered a bad enough result to warrant a change in direction?

Once a decision has been made to stop or alter an approach, it is then key to quickly figure out a new approach, iron out the deficiencies of the original method and run again (iterative development??).  This is just really a positive feedback loop.  The difficulty is, that the customer doesn't know they're being canvassed for their opinion.  They're simply being offered a product or service via a marketing, advertising or sales channel and either converting as a purchaser or ignoring.  As the product owner or seller, it's then key to either try and understand individually why the conversion failed or strategically if a failure occurred across a larger group.

Like in software, you can't create a product/feature in isolation from the people who will use it.  You can create the most beautifully complex piece of code in the world.  If no one uses, needs or likes it, it's not really doing it's purpose.  Conversely you'll often find the most hacked up, short term, sticky plaster of an approach is massively successful, loved and used beyond all expectation.  Both of those circumstances can be normalised if a solid feedback and rescoping process is run.

Popular posts from this blog

Customer Data: Convenience versus Security

Organisations in both the public and private sector are initiating programmes of work to convert previously physical or offline services, into more digital, on line and automated offerings.  This could include things like automated car tax purchase, through to insurance policy management and electricity meter reading submission and reporting.

Digitization versus Security

This move towards a more on line user experience, brings together several differing forces.  Firstly the driver for end user convenience and service improvement, against the requirements of data security and privacy.  Which should win?  There clearly needs to be a balance of security against service improvement.  Excessive and prohibitive security controls would result in a complex and often poor user experience, ultimately resulting in fewer users.  On the other hand, poorly defined security architectures, lead to data loss, with the impact for personal exposure and brand damage.

Top 5 Security Predictions for 2016

It's that time of year again, when the retrospective and predictive blogs come out of the closet, just before the Christmas festivities begin.  This time last year, the 2015 predictions were an interesting selection of both consumer and enterprise challenges, with a focus on:

Customer Identity ManagementThe start of IoT security awarenessReduced Passwords on MobileConsumer PrivacyCloud Single Sign On
In retrospect, a pretty accurate and ongoing list.  Consumer related identity (cIAM) is hot on most organisation's lips, and whilst the password hasn't died (and probably never will) there are more people using things like swipe login and finger print authentication than ever before.

But what will 2016 bring?

Mobile Payments to be Default for Consumers

2015 has seen the rise in things like Apple Pay and Samsung Pay hitting the consumer high street with venom.  Many retail outlets now provide the ability to "tap and pay" using a mobile device, with many banks also offer…

The Role of Identity Management in the GDPR

Unless you have been living in a darkened room for a long time, you will know the countdown for the EU's General Data Protection Regulation is dramatically coming to a head.  May 2018 is when the regulation really takes hold, and organisations are fast in the act on putting plans, processes and personnel in place, in order to comply.

Whilst many organisations are looking at employing a Data Privacy Officer (DPO), reading through all the legalese and developing data analytics and tagging processes, many need to embrace and understand the requirements with how their consumer identity and access management platform can and should be used in this new regulatory setting.

My intention in this blog, isn't to list every single article and what they mean - there are plenty of other sites that can help with that.  I want to really highlight, some of the more identity related components of the GDPR and what needs to be done.

Personal Data On the the personal data front, more and more org…