I don't work in either of these fields, but I work closely with people that do, however, I'm writing this through my lens as a senior project manager and business analyst, as I feel it puts me at a vantage point to relate closer to how clients think at a project delivery level.
In a climate where clients expect cheaper systems delivered by projects with aggressive timelines there are some core activities that surround a delivery project that needs to be excluded. Activities in the UX/CX space are often the casualty.
Well herein lies the point. Good UX/CX practitioners explore, confirm, and resolve all these issues! They can also do most of this concurrently with system delivery.
In an earlier article, I wrote about personalisation, and I talked about how fickle customers are these days, well that doesn't just apply to content, rather the entire experience they have with your website or system. This directly feeds into their opinion towards your brand. If one of these is tarnishing the other, you're limiting growth.
There seems to be a slight misunderstanding who you can go to for services like this, a lot of companies go to well-known digital marketing agencies for branding and corporate identity design and then naturally just throw all related work in the same direction by default. Is this the right move? Probably not.
As soon as you cross into the application space, the skills needed by the same disciplines change. They're stronger. They're deeper. They're completely aligned with the engagement points you're actually going to have with your customers. It's moved from the 'theoretical' space into the 'actual' space. And the best part? Under agile delivery, you now have a whole lot more options and tools to make sure you're headed in the right direction.
Leveraging LEAN you can get system releases, features or configurations implemented and deployed with as little expenditure as possible. You can then solicit feedback from customers, or even just monitor their interactions. You can do A/B testing with live transactions instead of focus groups that marketing agencies often use. Instead of designing how it should be and hope it works, you can validate on the fly and actually make it work that way.
Delivery teams almost always have a UX/CX resource assigned in some capacity, so the outcome of those tests can directly trigger the response of change, to tune and hone the touchpoint to execute exactly as you want. It often even surfaces more touchpoints that may not have been planned for.
So my advice to you? When planning your digital project, determine your budget as usual, but then appeal to your project sponsor to zoom out a little to the digital transformation level within your organisation. Acquire a little more budget at this level to truly engage with UX/CX activities.
The ROI might not be as immediately obvious as when a new system goes online, but it's an insurance policy in the form alignment to other strategy items you're executing at a company level. It will address consistency, cross system friction points, and even potentially simplify your architecture and the administration needed to run it.
More importantly, it will ensure your customers have a consistent and managed experience with your brand. Let's face it, as customers, that's what we love, and that’s what keeps us coming back.
Our UX team is currently working on some great brochures that really explain our offerings as stand-alone services de-coupled from our delivery projects. They also have a blog post in the works coming soon so watch this space.
With so many options, how can you ensure you're making an informed decision and truly comparing apples to apples? Our selection criteria checklist is here to guide you. By asking the right questions and focusing on what truly matters, you can streamline the process and set your project up for success from the start.
One of the biggest fears technology buyers face is overpaying for a solution from a software development company. It’s a valid concern—nobody wants to invest significant budget only to feel they didn’t get what they paid for.
Technology leaders embarking on custom software development projects often fear non-compliance with industry standards. This fear is well-founded, as failing to adhere to regulatory requirements can result in severe penalties, legal actions, and damage to the company's reputation.
Whether you’re curious about custom software or have a specific problem to solve – we’re here to answer your questions. Fill in the following form, and we’ll be in touch soon.