As a professional Engagement Architect and User Experience consultant, I had questions.
Fortunately, I also had a framework:
Always the first UX question
1.0.1 How hungry were the children and parents waiting for me to order for them?
Create personas for users, and prioritize their needs
18.104.22.168 When would the inevitable meltdowns begin?
Time the rollout of phases and features for user acceptance and engagement
2.0 If I left the line to get another cocktail, should I (a) come back at the end of the fast line, or (b) ask someone in the slow line to hold my place?
Consider and plan for social options
And then a phone behind the counter rang, revealing the workflow issues throttling the slow line, and proving once again that there's no substitute for observation in the field in UX work.
Figure 1: Customer Service Workflow: Chicken Fingers ʻnʼ Beer Place for After Soccer
This was amazing to behold:
i. Two cashiers.
ii. Two lines.
iii. One phone.
iiia. The cashier on the slow line answers all the phone calls
I perceived a pattern here, and I had questions:
(a) How many people in the slow line had no idea they were also effectively in line behind people calling on the phone?
(b) How many noticed?
The situation reminded me of the debacles at airport gates when flights are cancelled and some people start banging on and shrieking away at their phones, while others remonstrate with the ticket agents.
I had a proposition to test: What if, while I was standing in line, I called my order in?
Would I see the cashier answer the phone and take my order ahead of, well, me?
I pondered the ethics, until it was my turn.
And I thought about how situations like this are everywhere, and how the questions around them are always the same:
- What will it take to fix this?
- What is the price of not fixing it, vs. letting things continue as they are?
At the chicken shack, the possible solutions are obvious. Only one phone? Get another. Too short staffed? Staff up.
What are the issues where you are? How would fix them?