This is near how I conduct business, as I cannot keep track of everything, nor can I have a non-stop scribe to note and catalog things.
AWS and several others use this in interviews.
I use STAR/SPAR:
[S]ituation or context
[T]ask or [P]roblem
[A]ction or solution
[R]esult or expected outcome
Basically, tell me the background, tell me the problem or thing that needs done, tell me all the ways it was reviewed, and the actual picked solution or action, and finally what is the expected outcome or result. As an exec I can be a stateless machine and with that set of details, I can make a decision.
Sometimes I dig into it a bit to see if proper due diligence was done, if there is real info & data is present, but once I am comfortable that the person distills it properly, it is a no brainer decision. I can say, "yes, go forth with your action/solution" or "no, because XYZ, go back and consider that" (usually from the T/PA/R areas).
There might be a way to craft this for story telling, after all, most things are stories.
AWS and several others use this in interviews.
I use STAR/SPAR:
[S]ituation or context
[T]ask or [P]roblem
[A]ction or solution
[R]esult or expected outcome
Basically, tell me the background, tell me the problem or thing that needs done, tell me all the ways it was reviewed, and the actual picked solution or action, and finally what is the expected outcome or result. As an exec I can be a stateless machine and with that set of details, I can make a decision.
Sometimes I dig into it a bit to see if proper due diligence was done, if there is real info & data is present, but once I am comfortable that the person distills it properly, it is a no brainer decision. I can say, "yes, go forth with your action/solution" or "no, because XYZ, go back and consider that" (usually from the T/PA/R areas).
There might be a way to craft this for story telling, after all, most things are stories.