Intelligent CXO Issue 37 | Page 27

BUSINESS STRATEGY
Lower the barrier to entry
Technology can be intimidating , especially to non-technical people . For any developers reading this article , consider the first time you come across a new tech stack or tool . That feeling of intimidation or imposter syndrome might be ever-present for someone who is non-technical . For your solution to be used , it needs to be simple with relevant automations .
Allow for regular user feedback
For proper adoption of your solution , you need to be guided by your user . This can be guided by a persona – the actual person who most accurately represents your userbase and whose opinions should guide your development . For example , perhaps they prefer a blue button over a green one and therefore , we should favour their feedback . One needs to build for what our users need versus what we think they need . Beyond this , with regular feedback you are more likely to hit your targets .
Keep it simple stupid ( KISS )
Use simple language and sentences , especially in documentation . Complex language will prevent people from understanding what you have built and may prevent it from being used . Images and flowcharts will often explain more than words .
Trust is earned and not given with clients
Trust with clients is earned through honesty , ethics and genuine commitment to their best interests within the agreed scope . Improvements that are out of scope can be placed on a backlog which shows commitment to improving clients ’ environments .
Trust can also be built by showing clients that you take care of the work that you do . My colleague , Nikeel Sathoo , summed this up perfectly . Sathoo suggested that rather than diving into developing a solution , for example ; on a call with clients , take a step back from the interaction , do your research for a reasonable amount of time and then come back with a solution .
Not only will this ensure that your approach is strong , but it will show the client that you want to get the right solution for them , rather than a generic one that might address some of the immediate concerns but may not scale to others that are less obvious .
Navigating the nuances of project delivery within a client domain can be incredibly challenging , but with a communication-driven approach , this can be made much simpler . x www . intelligentcxo . com
27