Should Developers Know the Business Customers?

We often hear that we need to ‘know our customers.’ We need to know what their needs, wants, and desires are.

What made Steve Jobs so great at what he did was that he intimately knew what his consumer base wanted… and then created the best darn product out there. He revolutionized the way we listen to music, and changed the way we interact with technology.

As developers, we often can have a tendency to want to create something that we seriously think will be helpful or useful to others. We want to make the best products and we want to add those features that… well, we would use. We hate wasting time.

Often though, this doesn’t exactly fall in line with what the real customer might want.

“But it’s new and cool, dude.”

We hear statistics around how much of the features of a product aren’t used. I mean, look at Microsoft Word or Excel. I would bet that 95% of those features aren’t used. What the heck?

In Agile/Scrum we have a Product Owner, sometimes a┬áliaison, or representative of the customer. What would happen if we have the team show off the software to actual customers, get revisions and edits, and build what they want? I’m working with a company right now in which I suggested they do just that: Put their development team in a position to speak with customers. So far? It’s working.

Now, I wouldn’t suggest that all companies do this, but for this particular situation it works.

Deploy. Show your customers, get feedback. Inspect, adapt, refine. Improve. Oh wait… yes, that can include the whole agile team and developers too. :)

FacebookTwitterLinkedInShare

18 Responses to “Should Developers Know the Business Customers?”

  1. Tom
    November 15, 2011 at 11:36 am #

    If your customers are likeable and can articulate what they need and why they need it it can be great to meet up. It can be really motivating for the team.
    I think true collaboration with customers is the holy grail – a customer as part of the team. So hard to achieve in most cases.

    • peter
      November 15, 2011 at 11:39 am #

      Ha! Sometimes… they aren’t easily liked…

  2. MktgMeetsIT
    November 15, 2011 at 11:34 pm #

    I agree with Tom – the potential is there for the kind of collaboration that is the very essence of the Agile Manifesto. And I’ve seen it work well.

    I don’t agree likeability should be a prerequisite, though. The biggest ratbastard stakeholder on the planet who can communicate clearly and concisely what needs to be built will drive progress more effectively than an affable, pleasant, stream-of-consciousness stakeholder who couldn’t communicate an intelligible user story with two whiteboards and a hand puppet.

    • peter
      November 16, 2011 at 9:16 am #

      Ha. Ratbastard. Epic. I think maybe… having a liaison there may help grease the wheels of communication..

    • Jay Decker
      November 16, 2011 at 11:32 am #

      I believe it depends on how your developers handle themselves with respect to customer interaction. You may experience disruption when your talented yet introverted engineer clashes with said ratbastard. Given your environment, the “product owner as a meatshield” strategy may be well suited.

      • peter
        November 16, 2011 at 12:22 pm #

        Or a ScrumMaster meat shield

  3. David J Bland
    November 21, 2011 at 10:02 am #

    When developers understand the customers, they become entrepreneurs or intrapreneurs. Why would they want to be labeled as a just a developer any longer?

    • peter
      November 21, 2011 at 10:03 am #

      So… what about this: Not calling a developer a developer.. but team member? OooOOoo

      • Jordan
        November 28, 2011 at 4:48 am #

        They’d still want extra pay OooOOoO :)

        Seriously tho — this devs meet customers is wishful thinking imho. There is a reason there are geeks, and there are smoothy salesmen/customer relations people, and that they are different people.

        If you really had someone who was both, not only would they be few and far between, but they’d be entrepreneurs starting their own business and not easily available in the labor pool.

        Maybe in Japan the engineers are presentable enough to work in a car dealership for a few months ala the toyota way, but most software devs are not.

        Also a single point of contact for the customer has always made sense, and I think that too much interaction can muddy that aspect.

        Bottom line: Sales owns the customer and sales isn’t going to put developers they don’t know personally in front of their customer. See wishful thinking above :)
        Jordan
        Jordan

        • Tom
          November 28, 2011 at 6:07 am #

          IMHO passing information like this through sales is the root of the problem. Sales have their own agenda (to hit targets) and will often twist the users story accordingly to try to keep both parties happy. They also make there own assumptions about what’s easy/difficult to do and miss the best solution to a problem. If you want a good product you need to cut out as many middlemen as possible between the user and the developer.

          Some developers may lack experience at dealing with customers but that doesn’t mean it isn’t something they can learn. In the right context customers are find it refreshing to speak to a straight talking developer and will make allowances for their possible lack interpersonal skills. Modern dev teams that collaborate constantly don’t lack these skills anyway.

        • peter
          November 28, 2011 at 12:12 pm #

          Why not try it out? Wouldn’t it be valuable to try and see? It may not work for every company, but I would bet that some companies would… benefit from it… potentially. Wishful thinking!

Trackbacks/Pingbacks

  1. Should Developers Know the Business Customers? | Agile | Syngu - November 16, 2011

    […] We often hear that we need to ‘know our customers.’ We need to know what their needs, wants, and desires are. What made Steve Jobs so great at what he did was that he intimately knew what his consumer base wanted… and then created the best darn product out there. He revolutionized the way we […]You just finished reading Should Developers Know the Business Customers?! Consider leaving a comment! We run our blog on Standard Theme. Be a writer for us. Post a job with us on Agile Jobs.    Agile Read the original post on Agile Scout… […]

  2. Should developers know about their customers? « Best of Agile - November 16, 2011

    […] http://agilescout.com/should-developers-know-the-business-customers/ Share this:TwitterFacebookVind ik leuk:LikeWees de eerste om post te waarderen. […]

  3. Retrospective 59 – Agile Sucks… and the Answer? | Agile Scout - November 21, 2011

    […] Should you allow your developers to meet the business customers? […]

  4. Transparency as a Customer Builds a Relationship » Agile Scout - August 22, 2012

    […] in the market for a customer feedback solution. There’s tons of them out there. After putting together a list and culling down to the […]

  5. Why Customers Still Need Voices » Agile Scout - September 4, 2012

    […] think customers’ communications with product management and product marketing is way better now with Social – probably so but when are the voices […]

  6. If a Customer Asks “Can You Hear Me?” Will Anyone Hear? » Agile Scout - September 12, 2012

    […] You don’t build stuff (applications, databases, software, apps, websites) for yourself. You build these things for your customer. […]

  7. Retrospective 59 - Agile Sucks... and the Answer? | Agile ScoutAgile Scout - August 30, 2013

    […] Should you allow your developers to meet the business customers? […]

Leave a Reply