The Galvin Blog
Our blog serves as space for us to share news and ideas about project management, website development and interactive design. Enjoy.
Even Waiters Have Problems Acquiring Requirements from Clients
Posted By : Crissy Koger Posted On : January 26th, 2012
Topics : Business Strategies, Discovery, Galvin Processes, Project Management
I was getting some work done at a local restaurant this morning and overhead a waiter taking an order from a customer. The customer ordered a main dish and included, “I’d like to substitute the fruit cup for the potatoes.”
If you are like me, I took this to mean that the customer wanted potatoes. When the order came up, the customer replied, “Oh, I asked for the fruit cup.” Since overhearing the original order take place, I began to think about what exactly the customer asked for because I’m in the business of gathering requirements from clients so this was all too familiar to me.
Original Requirement: “I’d like to substitute the fruit cup for the potatoes.”
Now this requirement could have been interpreted two ways:
- Customer wants fruit instead of the potatoes.
- Customer wants potatoes instead of fruit.
The waiter had a 50/50 chance, in this case, to get the client’s expectations correct. However, the waiter (and I) assumed incorrectly. This could have been easily corrected by just repeating back to the customer, in the waiter’s own words, what the customer wanted: “You would like to have a side of potatoes?” The customer could have corrected the waiter during this point versus having to wait until the order was delivered to only find out it was wrong.
This can happen all too often in any industry, but we experience it a lot in the software development field. You may have seen the infamous comic strip of the “tree swing”, as shown below:
There’s always a small chance for error when acquiring and understanding requirements from clients. Hey, we’re all human, right? But you can help ensure you get them 99% right just by using the following three tips:
- Repeat the request using your own words. Try not to use technical terms. Clients can have a different definition than you or may not admit they don’t know what you mean.
- Draw a picture. A picture speaks a thousand words.
- Ask the question a different way and see if you get a different answer.
Remember, you never know when the client might want fruit and you give them potatoes.
Subscribe to our blog
Topics
- Application Development
- Business Development
- Business Strategies
- Community
- Content Development
- CRM
- Design
- Discovery
- Ecommerce
- Galvin Culture
- Galvin Processes
- Interface Design
- Mobile CRM
- Mobile Development
- Mobile Web
- New Technology
- Philanthropy
- Photography
- Project Management
- Social Media
- Software Engineering
- Uncategorized
- User Experience Design
- Viral Marketing
- Web Development
- Website Marketing

Comments