Hi All, I am looking for some best practice advice on how walk the interviewer through your structure. Any examples would be great
Walking interviewer through the structure


Hi there,
Are you referring to how to communicate the structure, once you are ready to present? If so, I would recommend the following as general steps:
- Present the first level, then the second level: “So given the goal XXX, I think we could look at 3 main areas: first ABC, second DEF, third GHI. If ok with you I would like to go deeper into each”
- Use numbers/clear bullets when presenting levels: “In the first area I would like to look at the following: First…, Second..., Finally..."
Ideally, you want to personalize the words you use according to the case (so, don’t say “price” or “volume” but, for example, “average monthly payment for the software” and “number of software licenses”).
If you want to get detailed feedback on a particular structure, I would recommend to write down your approach, so that we can comment on that specifically.
Hope this helps,
Francesco

Very simple - top down communication!
It goes something like this:
“In order to achieve X, I would like to explore 3 areas: A [name], B [name], and C [name]. Within A, I have 3 areas I'd like to zoom in on: 1 [name], 2 [name], and 3 [name]. As for 1, I my hypothesis is this and that, as for 2 it's this and that, as for 3 it's this and that. Now, let's look into my second bucket B, where I have 4 areas I'd like to zoom in on: ….”
Hope you get the point. This is difficult to master but very important because otherwise you'll loose the interviewer, especially during remote interviews where they can't peak at your sheet.
Hope this helps a bit! Best of luck!

Hi there,
Francesco's post pretty much nails it. Here my thoughts..
- Present Layer 1 first (high-level)
- Deep dive into Layer 2, branch by branch (if need)
- Get ‘sign-off' - validate with the interviewer
Please note i'm adding 3 here, which is very important - validating your structure / framework with the interviewer ensures alignment early on and minimizes the potential “margin of error”, means it significantly reduces the risk that you run in the wrong direction.
A good way to execute that is using closed questions (Yes/No) to make the interviewer commit - something along the lines of…
- "Does this approach sound reasonable to you?
- “Any critical parts the structure is missing / we should ignore?”
Hope this helps. Feel free to reach out if you have further questions.
Regards, Andi

Hi there,
Step 1 - Signpost
Flag the key buckets. Avoid being generic, i.e. not just “Market” and also provide a single sentence to articulate the “Why” of the bucket
Step 2 - Dive in
Go through each bucket individually, talking through what you're going to look at and how it will help answer the objective. Make sure you have sub-structure here!
Step 3 - Summarize (optional)
If needed, give a summary sentence that makes it clear how your framework is actually going to help you address the objective!










