This is actually a recognised web site design rule described by Wikipedia as followsThe three click rule is an unofficial web design rule concerning the design of website navigation. It suggests that a user of a website should be able to find any information with no more than three mouse clicks. Another view or definition is The theory that users will abandon a website if they are unable to complete their task within 3 mouse clicks.
This functional simplicity is not easy to achieve but it repays the extra design and build effort many times over. By contrast I cannot count the number of projects designed to improve professional practices I have been involved with which foundered in a sea of complexity. The results if they ever saw the light of day were never going to be widely adopted. Potential users were turned off from the start by the intricate interfaces weaved to do justice to the system or process.
I sometimes think this happens because a project team gets carried away in the details and forgets the objective they were set up to achieve. Instead it becomes a sort of self-fulfilling prophecy which satisfies the (sometimes increasing in number) team members but does not deliver. Perhaps it is all about keeping the big picture in mind and embracing simplicity. The people in a team who bring you back to the objective and keep seeing the wood for the trees are invaluable.
This is recognised in the context of software development projects where it even has a name - The Software Peter Principle is used in software engineering to describe a dying project which has become too complex to be understood even by its own developers. It is well known in the industry as a silent killer of projects, but by the time the symptoms arise it is often too late to do anything about it. Good managers can avoid this disaster by establishing clear coding practices where unnecessarily complicated code and design is avoided.
There is also a book The Mythical Man-Month: Essays on Software Engineering by Fred Brooks first published in 1975, with subsequent editions in 1982 and 1995. Again according to Wikipedia Its central theme is that "adding manpower to a late software project makes it later".Brooks' observations are based on his experiences at IBM while managing the development of OS/360. He had added more programmers to a project falling behind schedule, a decision that he would later conclude had, counter-intuitively, delayed the project even further. Too many cooks spoiling an already complicated broth.
The same is absolutely true in communications. I recall a Queen’s Counsel dictating a letter to me over the phone in a complex dispute off the top of his head, which was impressive in itself. The draft was perfect in its simplicity, elegant and sticking to the point. There were no hostages to fortune. By contrast I have often seen over the last few years what should be simple communications over complicated to the point where at best they cause confusion and at worst defeat their purpose.
Winston Churchill is one of the best exponents of simplicity in writing. On August 9, 1940, with the Battle of Britain raging in the skies above England, Churchill wrote the memo to his staff I set out at the start of this blog encouraging them to write shorter and more concise reports avoiding “woolly phrases” such as “consideration should be given to the possibility of carrying into effect….."
Ultimately you need to have the users or audience in mind as you build systems or processes or more generally communicate. Abraham Lincoln said “When I get ready to talk to people, I spend two-thirds of the time thinking about what they want to hear and one-third thinking about what I want to say.”
As Leonardo Da Vinci commented “Simplicity is the ultimate sophistication”.


RSS Feed