Have to say – all 20 points resonate – but strong argument to suggest that the author pay heed to his own advice. Why not structure the 20 points into the order of how to attack the problem, group them logically, provide consistent guidance – some of the visuals were very relevant – other not so – and others useless. Still – does not detract from a great list.
Most business presentations suck. They’re boring. They’re confusing. They’re out of touch. This gallery explains exactly why most presentations are so dreadful, and what to do make your own presentations better.
… By Geoffrey James
This just whipped into my inbox at speed this afternoon. I read it. It resonated – and I wanted to share it. Just see how the article opens up:
The benefits of customer and agile development and minimum features set are continuous customer feedback, rapid iteration and little wasted code. But over time if developers aren’t careful, code written to find early customers can become unwieldy, difficult to maintain and incapable of scaling. Ironically it becomes the antithesis of agile. And the magnitude of the problem increases exponentially with the success of the company. The logical solution? ‘Re-architect and re-write’ the product.
For a company in a rapidly changing market, that’s usually the beginning of the end.