It’s rare that I see something that I just have to stop and read, but Eric Fletcher recently shared a blog post, Making “Client-Centered” More than a Marketing Copy Point, that jumped out at me.
Maybe it’s because I’ve been spoiled by working at 352, but the term “client-centered” feels old fashioned – a vague promise to put the client’s objectives in front of the agency’s ego as it pushes forward through development or marketing initiatives.
Too often, “client-centered” is a descriptor of the work agencies produce, rather than a fundamental aspect of how the agency works.
One of the biggest benefits of our agile approach to custom web development and marketing is that it naturally takes us beyond “client-centered.” With the client participating in daily standups, grooming the backlog with a development team or approving a sprint plan for marketing, it’s easy to ensure that client priorities and input are always integral to our process.
Everyone talks about being client-centered. Those who back up all the talk with real substance are rare. ~ Eric Fletcher
“Client-centered” often means that a team works around the client, rather than with them. The client is kept on the periphery of the process and eventually a team will come back to show the development or marketing work they’ve created away from the client. That’s just gravity pulling them back, not an actual desire to include the client in what they produce.
Placing a client at the actual center of a project – and asking them to provide feedback and collaborate on a daily basis – does more than simply ensure a client’s needs are met; it creates true accountability and ownership of a project within a team.
For “client-centered” to truly be more than marketing copy, it has to be a fundamental aspect of the relationships you build, not just the work you create.