Communication is one of a problem solver's core competencies. NASA has put together a guide for its staff on writing technical reports and it's out there for free on the internet. While it can be of help in documenting your work, it is helpful in other ways.
Chapter 1, Stages of Report Preparation, could also be though of as a high-level overview of stages of problem solving.
Gathering of data,
analyzing to extract information,
outlining to highlight missing information,
writing to build knowledge, and
revision to perfect communication and knowledge transfer
When faced with a problem. Don't just jump in aimlessly, gather your data, analyze it to diagnose the problem better, outline possible solutions. Write (or implement) a solution and finally, revise the solution to perfect it and address any oversights or limitations.
One doesn't think of a methodical, organized person as creative. There's no eureka moment, frenzy of activity, or sudden change to point to. However, part of being creative is being prepared. Musicians practice long hours on very basic skills in order to have the ability to demonstrate artistry with ease. You can't play a concerto without having mastered tone and articulation. Despite what one might think, making music doesn't come naturally.
Problem solvers should build up a database (some might call it a repertoire) of information, techniques, and connections. You never know what might be of importance in addressing a problem you encounter. If you haven't toyed around with something, you won't know it's capabilities when faced with a problem. I've posted on this topic before, perhaps more specifically. Take time to learn new skills, play around with things, and build up a database of information in order to be prepared for your next eureka moment.
Posts
