you are given only 2 hours to analyze the checkout process of a website ...
where would you begin?
Would you jump right to the cart page and review it?
Would you add products to the cart and actually make a purchase - reviewing each page along the way?
If the latter, which products would you choose?
How much time would you allocate for building the presentation?
Would you review data or just review the process without trying to understand the available data?
What if ...
2 hours is not much time - particularly if the data is available - because you must use it if at all possible.
Does it make sense to push back and request additional time?
You bet.
Does it make sense to request a meeting to discuss what has been tried (if anything) -- to gather some history, some perspective, and potentially understand what plans have been made for updates?
You better.
Discovery is never a bad thing.
Discovery provides you, the analyst, with context and understanding. It also means that you may not head down the same road ... no reason to recommend something that is already on the "to be completed" list.
How would you know that unless you ask?
Discovery - it's the meeting where you learn what you don't know, where you ask questions that may seem basic - but are very important to capture. Take the time. Push back. Get the meeting before the expectation of a completed analysis even enters their minds.
Details. Details. Details.
Process. Process. Process.
The analytic process must always begin with discovery -- even when you work for the company rather than in an agency/client situation: discovery is merely a means to gather needed information prior to starting the analysis.
Comments