Booking Engine (WIP)
This is basically a shot of a booking engine that my team and I have been working on during a three day sprint. Upon looking at the goal and the requirements document that came with it, I found it deceivingly simple in how it was explained. Naturally, this kind of set me off into my relentless inquisition routine asking 'why?' every step of the way.
As with every project, asking 'why' can help uncover the hidden complexity that was just lying there, ready to be tackled. And so knowing this, I found it important that the team and I made sure we didn't lose sight on what kind of problem or tension we were trying to solve.
After a bunch of research, sticky notes a plenty, reading, researching, talking to people and a lot of feedback we produced some quick prototypes that tried to tackle that problem (which then further boiled down into sub-problems).
For people using our product, we were trying to make sure that the feeling of price transparency and comprehensiveness (to make sure personal possessions are taken care of accordingly) were engrained into the touchpoints leading up to the purchase decision. Whereas for the business, we were trying to make sure that more people gave enough information so that there was a better understanding of the job to be done.
We still have a lot of work to do, but we really did get far especially in three days (well five if you include all the feedback and iterations we went through).