Go with the Flow – How to Organize Your Technical Presentation to Get Business Results – Part 4 – Issue-Resolution Structure

During my time in the IT industry, it became clear to me early on that technologist have to have mad problem solving skills.

Using existing technology, trying to meet the needs of the business, finding a work-around for an unusual need.  Great technologists are master problems solvers.   So of course a discussion of the organization of the most common technical presentations has to include the Issue – Resolution Structure

 

4.  Issue – Resolution Approach

Called my many names, this approach general boils down to a combination of:

Here’s the problem

Here’s how we got here

Here’s what we consider as options

Here’s our recommendation

What do you want to do?

In some ways, it’s similar to the Start with the End Approach.  But with certain analytical audiences, you will want to help them see the logic as to how you got to your conclusion so that they can evaluate the means before they judge the end.

 

What else?

What other structures do you think apply most commonly to technical presentations?

When might a combination of these approaches are needed and why?

Do you have a situation that won’t fit into one of these?

Love to get your feedback in the comments below!