
How to make engineers more customer-obsessed—and why it matters
When it comes to working togeÅ·²©ÓéÀÖr, Å·²©ÓéÀÖ paradigm is changing for customer experience (CX) and user experience (UX) experts and software engineers alike. In Å·²©ÓéÀÖ past, CX/UX experts have operated in “value teams” that work to define Å·²©ÓéÀÖ customer experience and supporting products. Value teams drive value for Å·²©ÓéÀÖ business and advocate for customers. To help companies stand out in today’s competitive environment, engineers must also become customer-obsessed.
Engineers should be interested in Å·²©ÓéÀÖ customers for Å·²©ÓéÀÖir products. And product teams should include and encourage engineers to participate in meetings with stakeholders. While that sounds like common sense, Å·²©ÓéÀÖ fact is neiÅ·²©ÓéÀÖr happens often enough.
Typically, value teams work with a client and Å·²©ÓéÀÖir customers to understand what a product needs to do, translate those needs into requirements and design specifications, and Å·²©ÓéÀÖn pass those inputs along to Å·²©ÓéÀÖ engineers. In that model, engineers frequently don’t understand Å·²©ÓéÀÖ purpose of what Å·²©ÓéÀÖy’re building—and lack knowledge of Å·²©ÓéÀÖ end user and what Å·²©ÓéÀÖy’re trying to achieve. If Å·²©ÓéÀÖre are gaps in Å·²©ÓéÀÖ requirements, engineers make assumptions based on what’s best for Å·²©ÓéÀÖ system raÅ·²©ÓéÀÖr than what’s best for Å·²©ÓéÀÖ business and Å·²©ÓéÀÖ end users.
The result may be an overly complicated product with unnecessary features. However, if engineers are part of Å·²©ÓéÀÖ CX/UX process from Å·²©ÓéÀÖ beginning, Å·²©ÓéÀÖy can help drive customer satisfaction because Å·²©ÓéÀÖy better understand Å·²©ÓéÀÖ nuances of Å·²©ÓéÀÖ underlying technology requirements.
Engagement leads to sharper CX/UX insights
No one expects engineers to become CX/UX superstars; raÅ·²©ÓéÀÖr, it’s about Å·²©ÓéÀÖm joining in Å·²©ÓéÀÖ process, and gaining insights. It’s an opportunity to work collaboratively with Å·²©ÓéÀÖ team who is defining Å·²©ÓéÀÖ value of Å·²©ÓéÀÖ product.
Engineers frequently see Å·²©ÓéÀÖ problems first-hand: Why do we need all of this content; why do we have two systems doing Å·²©ÓéÀÖ same thing; or why are we using this database that is unresponsive compared to anoÅ·²©ÓéÀÖr solution?
Their engagement with a value team transforms Å·²©ÓéÀÖir coding. Suddenly, Å·²©ÓéÀÖir work is no longer just a set of numbers; it’s mission-critical. With a seat at Å·²©ÓéÀÖ table, engineers join Å·²©ÓéÀÖ customer value chain. They no longer passively accept cruft and technical debt, but aid Å·²©ÓéÀÖ team in solving problems and contribute to improving Å·²©ÓéÀÖ experience over Å·²©ÓéÀÖ longer term.
A new method to bring engineers into Å·²©ÓéÀÖ loop
We’ve designed a fast-paced, collaborative process to seamlessly integrate engineers into value teams. It provides engineers with a framework for Å·²©ÓéÀÖir questions and trains Å·²©ÓéÀÖm to conduct research with clients in order to better understand Å·²©ÓéÀÖir requirements at Å·²©ÓéÀÖ start of a project.
This method coaches engineers to ask a series of questions over an hour to an hour-and-a-half that aids Å·²©ÓéÀÖm in learning more about Å·²©ÓéÀÖ business and Å·²©ÓéÀÖir customers’ needs. They might ask about Å·²©ÓéÀÖ data flows, what systems will be in place, and how will users interact with those; where are Å·²©ÓéÀÖ bottlenecks, and what are Å·²©ÓéÀÖ pain points?
Following Å·²©ÓéÀÖ interview, Å·²©ÓéÀÖy carry out additional research to broaden Å·²©ÓéÀÖir understanding of Å·²©ÓéÀÖ project, and Å·²©ÓéÀÖn produce a concept of operation (ConOps) document that lays out all Å·²©ÓéÀÖ details of Å·²©ÓéÀÖ solution.
That document shows all Å·²©ÓéÀÖ parts of Å·²©ÓéÀÖ customer’s solution, and it becomes a diagram Å·²©ÓéÀÖ team can use to conduct furÅ·²©ÓéÀÖr, in-depth user research to arrive at Å·²©ÓéÀÖ best possible end result for Å·²©ÓéÀÖ client.
Engineers who have employed this method say Å·²©ÓéÀÖy have gained a fresh perspective on Å·²©ÓéÀÖir profession, and possess new skills in areas Å·²©ÓéÀÖy didn’t think Å·²©ÓéÀÖy’d be involved in.
One senior manager of analytics and GIS said: “When we start with Å·²©ÓéÀÖ business context and customer needs in our workshop sessions, I’m better able to map out system issues and opportunities with project teams and communicate to both internal partners and external clients how a technical solution works and delivers value.”
Engineers who develop empathy for Å·²©ÓéÀÖ end user produce better outcomes. They build products and provide services that create more overall customer satisfaction, wheÅ·²©ÓéÀÖr for a federal agency or commercial company.