I can only do one thing. Solve problems. I am the one who provides the spark that other more technically minded and experienced people take and develop. I have a knack for spotting the bit people have ignored, the bit that was discarded early on which holds the key.
Areas Ian Stewart is Knowledgeable in:
Business delivery. Business operational problems.
Techniques Ian Stewart Uses:
mass application of possible solutions in order to prompt ideas in other people
consider all options
making a decision is normally the most important thing, once it is made it can be changed. 9 times out of 10, the best thing to do is to make the best decision you can with the information at hand...then modify it as you go...nothing like activity to get the creative juices flowing. Never ever ignore anyone's ideas...always listen...No such thing as a stupid idea...its just not relevant right now.
Ian Stewart's Problem Solving Skills:
Ian Stewart's Problem Solving Experience:
I have assisted a company to enter a flooded market and become no 1 in the marketplace in 2 years through being 100% contrary to the accepted norms for the industry.
One organisation I worked with was facing collapse due to not being able to attract operational employees. By changing their approach to recruitment so that they treated their potential employees like customers we reversed the problem completely.
I have patented a product that cuts door hanging times significantly for second fix carpenters.
I solve problems daily for business. All of these are my clients. Therefore descriptions must be in summary and details of solutions are confidential.
One of my clients started a new service complimentary to a product they were selling. (ie upsell the service to people buying the product) The service failed to attract custom due to an operational problem with delivering the service. Customers saw the problem and walked away. By taking a different approach to delivering the service, we successfully turned the problem around to become the services main competing difference.
I watched a software developer recently write 500 lines of code, and suggested a change in the way the problem was looked at which resulted in achieving the same result in just two lines of code.
I solved a problem for an animal sciences client whereby they can now remotely use a diagnostic instrument for wild / dangerous animals. By combining some commercially available technology with their existing instruments, the process can now be completed at a remove from the animal.