tag:blogger.com,1999:blog-45448030084611812952024-02-19T04:52:24.837-08:00Technical Problem Solvingmattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.comBlogger71125tag:blogger.com,1999:blog-4544803008461181295.post-68985090916974809852011-04-09T07:39:00.000-07:002011-04-09T07:44:49.931-07:00James Dyson and FailureI've posted regarding failure and problem-solving before. I came across <a href="http://www.wired.com/epicenter/2011/04/in-praise-of-failure/all/1" target="blank">this</a> by James Dyson on Wired.com, arguably one of the more famous inventors of our time and his thoughts on failure.<br /><br />Too often we're afraid to fail. Whether because of embarrassment, cost, or safety issues. However, it is one of the best ways to learn. Very few of us can manage to solve problems entirely in theory and place them into practice flawlessly.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-27431205570605281492010-12-10T18:58:00.000-08:002010-12-10T19:18:10.014-08:00Breaks versus InterruptionsIt is a good idea to take a break when working on a problem for a variety of reasons.<br /><ul><li>Overcoming mental blocks.</li><li>Getting a fresh perspective on a problem</li><li><a href="http://technicalproblemsolving.blogspot.com/2010/07/isolation-and-creativity.html?showComment=1280922079707#c4492087663760006081" target="_blank">Incubation </a><br /></li></ul>However, interruptions destroy the momentum you've built up. Some of the more obvious forms of interruptions.<br /><ul><li>Instant messages</li><li>E-mail notifications</li><li>Co-workers</li><li>Phone calls</li></ul>To remain productive you must take <span style="font-style: italic;">breaks</span> rather than experience <span style="font-style: italic;">interruptions</span>. The fundamental difference is that <span style="font-style: italic;">you</span> <span style="font-style: italic;">decide</span> when to take a break. <span style="font-style: italic;"> Other people</span> <span style="font-style: italic;">decide</span> when to interrupt you.<br /><br />If you're a manager, make sure the people that work for you are free of interruptions. Perhaps designate certain time periods where people can be off the grid, focusing on the difficult problems. Then other times when interaction is encouraged. Both are important and so you need to make time for both.<br /><br />If you're not a manager, perhaps block off time in your calendar, turn off the instant messaging and E-mail notifications so that you can't be bothered.<br /><br />I wonder if anyone has ever studied the workplace and the amount of interruptions that modern day workers encounter and the effect on productivity. Although we're more productive today because of technological advances, we may now be turning the corner where we are becoming less productive due to the inability to focus on problems.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-58536514145274937932010-11-05T16:24:00.000-07:002010-11-19T17:07:47.175-08:00Short Memory"<span style="font-style: italic;">You can’t improve a design when you’re emotionally attached to past decisions. Improvements come from flexibility and openness.</span>" A quote from the <a href="http://37signals.com/" target="_blank">37signals</a> blog.<br /><br />This brings me back to diverse thinking and confirmation bias. The longer we work on a problem, the more focused we are. The good part is that we tune out the unimportant and distractions, but the downside is that we are less open to a new insight which might lead to a better solution.<br /><br />How does one achieve a balance between focus and freshness? One way is to have several projects going at once (who doesn't) but rather than flitting back-and-forth in a feeble attempt to multi-task, I think you should dedicate significant chunks of time and effort to one problem. Then switch to another without re-visiting the first problem for some time. When you return to the initial problem you can't help but have a fresh perspective. You've also allowed for some incubation to occur. The longer you've worked on a project, the harder it is to return with a fresh perspective. That's where the challenge is.<br /><div><br /></div><div>The time spent devoted to one project is a factor you can play with. If it is a project you're familiar with, you can stay away from it for some time. For a new, unfamiliar project, don't stay away too long because you may end up spending too much time refreshing your memory.</div>mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-75223895438782422342010-11-01T12:37:00.000-07:002010-11-03T11:37:17.106-07:00Technical Report WritingCommunication is one of a problem solver's core competencies. NASA has put together a guide for its staff on <a href="http://grcpublishing.grc.nasa.gov/editing/vidoli.CFM" target="_blank">writing technical reports </a>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.<br /><br />Chapter 1, <span style="font-style: italic;">Stages of Report Preparation</span>, could also be though of as a high-level overview of stages of problem solving. <span style="font-style: italic;"><br /></span><ol><li><span style="font-style: italic;">Gathering </span>of data, </li><li><span style="font-style: italic;">analyzing </span>to extract information,<br /></li><li><span style="font-style: italic;">outlining </span>to highlight missing information, </li><li><span style="font-style: italic;">writing </span>to build knowledge, and </li><li><span style="font-style: italic;">revision </span>to perfect communication and knowledge transfer </li></ol>When faced with a problem. Don't just jump in aimlessly, <span style="font-style: italic;">gather </span>your data, <span style="font-style: italic;">analyze </span>it to diagnose the problem better, <span style="font-style: italic;">outline </span>possible solutions. <span style="font-style: italic;">Write </span>(or implement) a solution and finally, <span style="font-style: italic;">revise </span>the solution to perfect it and address any oversights or limitations.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-86248849245070059232010-10-30T12:13:00.000-07:002010-11-03T11:33:26.927-07:00Beautiful Tools<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://upload.wikimedia.org/wikipedia/commons/7/7b/Hammer2.jpg"><img style="float: left; margin: 0pt 10px 10px 0pt; cursor: pointer; width: 282px; height: 246px;" src="http://upload.wikimedia.org/wikipedia/commons/7/7b/Hammer2.jpg" alt="" border="0" /></a><br />An example of a beautiful solution. A hammer is simple yet can be used in a variety of situations (sometimes too many). It doesn't take a manual to understand how to use it. It is beautiful because of its simplicity. There's not much you can do to make it more effective. (Sure there are special hammers optimized for specific purposes, but that is a different kind of beauty). <br /><br />Probably every toolbox in the world has a hammer and if you don't, you've probably tried using other things in place of a hammer (your fist, a wrench, a rock) and found that they don't quite live up to the usefulness of the hammer.<br /><br />Just like Quality can be defined as fitness for use, Beauty (of a solution) is fitness for use. A hammer fits it's purpose. Nothing more, nothing less.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-13884366564014705082010-10-29T18:42:00.000-07:002010-10-30T12:00:58.622-07:00Beautiful Problem SolvingI have in interest in data visualization and there's a new book out there called <a href="http://www.shelfari.com/books/14210260/Beautiful-visualization", target="_blank">Beautiful Visualization</a>. That got me to thinking about whether solutions to problems can be beautiful.<br /><br />They can, but what makes them beautiful? There are characteristics the comprise the solutions whether they are a tool, a process, or a procedure. Simplicity, flexibility, completeness, complexity. What is of value depends on the situation and the user.<br /><br /><a href="http://en.wikipedia.org/wiki/Shaker_furniture", target="_blank">Shaker furniture </a>is famous for its simplicity and its functionality. What makes it beautiful is that it is both simple <span style="font-style:italic;">and </span>functional. Too simple and it would lose some of its functionality and would not be as beautiful. Finding that balance is an art.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-20734002638821014902010-10-26T17:26:00.000-07:002010-10-28T19:04:45.755-07:00Creation, Consumption, and CommunicationWe engage in three basic types of activities: <span style="font-weight:bold;">Creation </span>of new ideas, <span style="font-weight:bold;">consumption </span>of existing ideas, and <span style="font-weight:bold;">communication</span>, either of existing ideas or our own new ideas. Each of these has importance and there must be a balance among the three. <br /><br />I've posted about <a href="http://technicalproblemsolving.blogspot.com/2010/07/isolation-and-creativity.html", target = "_blank">Isolation and Creativity</a> before and there's a new book (and free e-book) about the need to <a href="http://zenhabits.net/focus-book/", target = "_blank">focus </a>in order to be productive. I've not worked my way through it (lack of focus I suppose) but it looks like the author will present various tools and techniques for eliminating distractions and the Data Smog that assaults us all the time.<br /><br />I've also posted about consumption (or learning). One should spend time being exposed to new ideas, getting inspiration from others. Consumption shouldn't just be of the things we like or that agree with our mind-set but should expand our ideas. Not that we blindly accept everything that comes our way, but that we are able to see things from another perspective. Nothing is more dangerous than someone who is certain they are correct. Doesn't matter where. As Nassim Taleb points out in the <a href="http://en.wikipedia.org/wiki/Black_swan_theory", target="_blank">Black Swan</a>, Experts are people who don't know what they don't know.<br /><br />And finally communication. Check the tag cloud for posts about that topic.<br /><br />There must be a balance of all three. We will be strong in one of these areas. You must cultivate your skills in the other areas. While being able to switch from one to another is important, don't get into the situation which the author of Focus describes where you flutter from one to another so quickly that you cannot build up any momentum. <br /><br />These three areas are a stool that your problem solving skills sit upon. Make sure each leg is strong and capable of supporting the weight of the problems you must address.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-52668960111727838712010-07-31T13:13:00.001-07:002010-07-31T13:34:50.665-07:00Unscientific America - Thoughts about communicationIn their book, <a href="http://lccn.loc.gov/2009015482", target="_blank">Unscientific America: How scientific illiteracy threatens our future</a>, Chris Mooney and Sheril Kirshenbaum make the point that it is not so much that Americans are not knowledgeable about science but that there is a lack of communication between scientists and the general public. The book examines many of the reasons for this but in reading the book, it brought to mind the "Curse of Knowledge" from <a href="http://technicalproblemsolving.blogspot.com/2009/09/getting-your-solution-to-stick.html">Made to Stick</a>. <br /><br />As scientists and engineers, we address all sides of a problem, considering the advantages and disadvantages and weighing their relative merits. This is vital, but once a decision has been made, one should consider simplifying things in order to more effectively communicate. To what extent one simplifies depends on the audience. In Chapter 5, Mooney and Kirshenbaum write about Preston Manning who distinguishes between "source-oriented communicators" and "<a href="http://www.interactions.org/pdf/SLAC_pavan_manning.pdf", target="_blank">receiver-oriented communicators</a>". Don't communicate from your perspective but "think about the audience and how to reach it". Are you talking to other engineers, to engineering managers, to business leaders, to the general public? Each of these audiences will need a different presentation tailored to their perspective.<br /><br />There is a difference between transmitting information and communication information.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-68686603875699765842010-07-24T19:44:00.000-07:002010-07-24T19:57:47.284-07:00Isolation and CreativityI've also come across a blog posting about the <a href="http://www.getfinch.com/finch/entry/the_creativity_trigger/", target="_blank">Creativity Trigger</a>. I might be misinterpreting it a bit, but one of the things the author mentions is being overloaded by information such that one doesn't have original thoughts but merely reforms what someone else has already done. Well he's a designer, and originality has more value in that area that for a scientist or engineer, but I think we can learn from him. While it is important to be <a href="http://technicalproblemsolving.blogspot.com/2010/07/networks-hubs-and-problem-solving.html">linked</a>, and exposed to many <a href="http://technicalproblemsolving.blogspot.com/2009/09/active-exploration.html">sources of information</a>, you should also balance this with times of isolation. This can bring new solutions, approaches, and strategies towards our problems. <br /><br />Like everything in life, we need to strike a balance in how we go about solving problems. You can't be everything at all times, so take the time to make a conscious shift in your approach from time to time.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com1tag:blogger.com,1999:blog-4544803008461181295.post-73180137370380314862010-07-24T19:24:00.000-07:002010-07-24T19:57:30.171-07:00Networks, Hubs, and Problem SolvingI recently finished reading <a href="http://lccn.loc.gov/2003282237" target="_blank">Linked: How Everything is Connected to Everything Else and What it Means.</a> In this overview of networks and the many places they appear in the world, the author mentions that there are hubs that connect different areas of the network to each other and they are key in getting information across the network. You may have heard of the <a href="http://en.wikipedia.org/wiki/Six_Degrees_of_Kevin_Bacon", target = "_blank">six degrees of Kevin Bacon</a> which is a game people play to relate any actor to Kevin Bacon based on movies they have acted in in common. The reason this game works is because there are actors who have acted in many movies alongside many other actors. Because of these actors who are 'hubs', actors who seem to have nothing in common are linked to each other.<br /><br />That brought to mind problem solving. If you are an expert in one area, but have no connections to other disciplines, your impact will be in a relatively small area. You only interact with others with a similar background and your problem solving will have depth but not breadth. Your network is isolated, or you rely on someone else to be the hub to network your skills and knowledge to other areas.<br /><br />Try to foster links in other disciplines, that way <span style="font-style:italic;">you </span>will be a hub that will transfer solutions to many areas, just the way a major actor links many actors together. Likewise, engage those from other areas since they may be working on things that are solutions to the problems you have.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-51785144349186206002010-07-07T18:18:00.000-07:002010-07-07T18:30:02.171-07:00Organization and CreativityOne 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.<br /><br />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.<br /><br />Here's Joan Rivers sharing about her creativity.<br /><object width="660" height="405"><param name="movie" value="http://www.youtube.com/v/87yztkvEsIk&hl=en_US&fs=1?rel=0&border=1"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/87yztkvEsIk&hl=en_US&fs=1?rel=0&border=1" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="660" height="405"></embed></object>mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-32818571921510753352010-06-24T19:22:00.000-07:002010-06-24T19:29:44.943-07:00More about FailureWe like to celebrate our successes. We have graduation parties, celebrate the completion of projects, a big sale, etc. It's easy.<br /><br />How do you deal with your failures? Do you try to forget about them, sweeping them under the rug? Maybe you're embarrassed about the failure or have been punished for the failure.<br /><br />I think it's important (perhaps after some time has passed) to review your failures to see what might have gone wrong. Is there something specific you can avoid in the future? Is there a pattern emerging where similar situations end up the same? Recognizing patterns is what we as humans are good at, but we need to be looking for them. Burying your head in the sand and hoping to forget about a bad experience increase the chances that you'll end up in a similar situation again.<br /><br />Also, leaders shouldn't punish people for failures (other than perhaps ethical failures - and certainly criminal failures). It will make them afraid to take risks, try something new, or be creative. How can you expect creative solutions to difficult problems if the consequences of failure are too great. <br /><br />Mistakes can be golden if you learn from them.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-85682588595083831322010-06-01T12:32:00.000-07:002010-06-01T12:39:07.806-07:00Overcoming Mental BlocksA quote from the <a href="http://37signals.com/svn/posts/2369-sometimes-a-design-isnt-working-because" target="blank">signal vs noise </a> blog. "Sometimes a design isn’t working because you think you can’t change the one element that needs to be changed"<br /><br />The same goes for problem solutions. Maybe you're not finding an effective solution because you are locked in on something as being essential when it isn't. Take a step back, attack the problem with a beginner's mind and maybe another solution will present itself. <br /><br />I was once faced with an analysis problem in which I couldn't avoid the compound I was trying to analyze decompose in the equipment. After many iterations of trying to find a way to avoid decomposition, I finally realized that if I deliberately decomposed the compound in a known manner, the solution was easy.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-63221069830264920372010-05-22T19:13:00.000-07:002010-05-22T19:19:03.729-07:00The importance of measurement.I was in recent discussion about quality and a couple of good points were made.<br /><ul><li>You cannot improve what you do not measure.</li><li>You cannot manage what you do not measure.</li></ul>Measurement helps to visualize problems and gives us perspective. Whenever you implement a solution, be sure to include measurements so you can evaluate whether the solution is truly effective. Ideally it is a measurement you were doing before you implemented the solution so you can quantify the improvement, but at the very least, include some measurements so that future improvements can be quantified. Sometimes it will take a couple of attempts to arrive at the optimum solution.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-18768057596720010062010-05-10T12:31:00.000-07:002010-05-10T12:37:24.377-07:00Lazy ThinkingPrejudice in problem solving is caused by lazy thinking. When we are pre-disposed to a particular solution, we need to be careful to avoid simply assuming the previous solution is the correct one this time also. This is related to the "beginner's mind". <br /><br />How do you strike a balance between re-creating the wheel every time a problem comes up and re-applying the same solution? It has to do with lazy thinking. If you carefully consider a problem instead of jumping to conclusions, it doesn't cost much in terms of effort and will help avoid overlooking potential new solutions or new wrinkles to an old problem.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-91058982422194526692010-04-28T12:34:00.001-07:002010-04-28T13:07:55.414-07:00Chartjunk or Communication?EagerEyes recently <a href="http://eagereyes.org/criticism/chart-junk-considered-useful-after-all">posted </a>about a study investigation the memorability of graphics and data. That brings to mind my earlier thoughts about communication. You may have the best data in the world but if it's not communicated well, then you've missed the target. I suppose which path you take depends on your audience.<br /><br />When you're presenting to an audience of a similar backround or perhaps more knowledgeable about that data than yourself, minimize chartjunk and seek to present the data in as unbiased a manner as possible.<br /><br />When you're the expert and are seeking to communicate the results of your interpretation, resist the "curse of knowledge" and incorporate some of the suggestions from <a href="http://lccn.loc.gov/2006046467" target="_blank">Made to Stick </a>to increase the memorability of the results and analysis. A perfect data presentation following Tufte's guidance may not be the optimal solution.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-37193632371372806332010-04-11T19:26:00.000-07:002010-04-11T19:38:09.927-07:00Expanding your SkillsI haven't posted much this year. My excuse is that I've been spending time learning PHP and Python programming. In the case of PHP It seems I don't have an immediate need for that knowledge but since it is commonly used to control many websites it seemed prudent to at least get a basic knowledge of that language.<br /><br />A knowledge of <a href="http://www.python.org", target = "_blank">Python</a> has been more useful. I expect that Python aficionados will give many reasons to use that language, but I've found it useful for processing text files generated by our lab equipment to create summaries so they can be processed by our software to input data in a LIMS. <br /><br />Don't be stagnant in your skills but continue to explore new areas. Some may not be immediately useful (like PHP in my case) and others will be. However, without exploring something new, you'll never be open to the possibilities that the new skill may present. Don't get stuck being happy with the status quo because you don't know what else is possible because your skills remain focused in a narrow area.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-16050932915692793192010-02-06T17:44:00.000-08:002010-02-06T18:41:50.814-08:00ImaginationI haven't posted in some time. It's probably a lack of imagination.<br /><br />Why is it that some people are content to do the same job, the same way over and over. I don't think it's that they're lazy. In most cases what they are doing is labor intensive. They might be very proficient and fast at what they do.<br /><br />I think it's a lack of imagination. They can't imagine doing it a different way. Not automated, not faster, not different. Just doing it.<br /><br />I follow a couple of blogs on Excel. The posts are mostly about customizing and automating so one can do things faster, and exactly the way you want them to be instead of relying on what the programmers envisioned. The desire to do things differently requires imagination about the way you want things to be.<br /><br />Work on your imagination and who knows where it will lead.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-83004789517230728782009-12-11T08:52:00.001-08:002009-12-27T18:09:26.227-08:00Fail=SuccessSorry for re-posting but not only does <a href="http://lifehacker.com/5423552/the-key-to-success-do-stuff?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+lifehacker%2Ffull+%28Lifehacker%29&utm_content=Google+Reader", target="_blank">this post</a> have good advice but I've recently come across the <a href="http://lifehacker.com/"target="_blank">Lifehacker </a>website. If you use computers (and what scientist or engineer doesn't), Lifehacker has many great tips, links to make your computing life easier. They are scouring the web so you don't have to.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-21646126281226089462009-11-27T09:43:00.000-08:002009-11-27T09:57:44.043-08:00DatabasesSome of my earlier posts have had to do with information (or data) visualization. Before you can visualize data, it must be readily available. In today's age of computers, your data is certainly electronic but if it is spread across multiple servers, directories, and files it is unmanageable and not available. This is where relational databases come in. <br /><br />If your data is in a well-designed relational database, you can access it in a variety of ways. Most data analysis software (e.g. Excel, MiniTab, Origin, Quality Analyst are a few that I've used) has wizards that make it easy to develop SQL queries to retrieve data. With a minimal knowledge of SQL you can modify the wizard queries to make them even more powerful. The <span style="font-style: italic;">important </span>part is to have your data in a database to begin with. While a LIMS or another database may seem like an expensive investment, it will pay off in the long run by giving you many opportunities to examine your data and find answers to your problems in data you have already gathered rather than having to design new experiments. <br /><br />In today's age of tight budgets, many companies want concrete justification for purchase and use of a database. The problem is that a database will help you solve problems that you haven't even imagined yet and so it is hard to provide evidence of the "hard" savings that a database will provide.<br /><br />Anybody with an eye towards the future (not just the next 3 months) should have a relational database for storing their data and begin inserting data immediately. Without data in your database, it will be useless.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-2218154003857769222009-09-28T18:05:00.000-07:002009-09-28T18:11:56.905-07:00Know your dataOften we gather data to aid in solving a problem we encounter. One trap that you can fall into is that the data is not exactly what you think it is. For example, you might be taking pressure readings from a process line to decide whether a filter is plugged. The pressure readings may be normal leading you to believe that the filter is not plugged and in satisfactory condition. However, if the pressure gauge is upstream of the filter, then the data is misleading you. The filter may be plugged but the pressure gauge location is misleading you. <div><br /></div><div>This is particularly a problem if you don't have good change control on your equipment. The diagram you are working on may not reflect reality. It is always a good idea to go look at what you're working on, both the help you visualize the process and to make sure things are as you think they are. The biggest danger to problem solving is thinking you can sit back in your office and just think through the problem. </div>Tech Problem Solverhttp://www.blogger.com/profile/00082055607681100379noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-66947286190504325232009-09-06T11:44:00.000-07:002009-09-06T12:02:13.014-07:00Active ExplorationWhen I was in school I was listening to a talk about a topic (or so I thought) unrelated to my research. The speaker mentioned in passing that they were adding hydrogen to the helium microwave plasma. That caught my attention as I realized that it may be suitable for the problems I was having getting my project on RF ICPs to work. With a little bit of literature searching I was able to find much work from the light bulb industry that addressed the problem that I was having. Imagine my surprise that my "research" problem had already been encountered (in a somewhat different form) in another industry.<br /><br />You should always be aware of potential solutions to problems you might encounter in unexpected places. In "Made to Stick" the authors talk about the power of spotting a good story that supports what you want to communicate. Unless you are actively looking for such an story, you may miss it when you come across it. Likewise problem solutions may elude you unless you have the problem(s) in mind and you are actively looking for solutions. <br /><br />Don't neglect this <a href="http://technicalproblemsolving.blogspot.com/2008/10/essential-ingredients-of-problem.html">key ingredient of problem solving</a>.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-19592753435340838142009-09-06T11:22:00.000-07:002009-09-06T11:41:43.989-07:00Getting your solution to StickIn their book "<a href="http://lccn.loc.gov/2006046467" target="_blank">Made to Stick</a>" Chip and Dan Heath make the following statement (slightly edited) in the Epilogue.<br /><br />"[Problem solving] has two stages: the Answer stage and the Telling Others stage. In the Answer stage, you use your expertise to arrive at the [solution] you want to share. [...]<br />Here's the rub: The same factors that worked to your advantage in the Answer stage will backfire on you during the Telling Others stage"<br /><br />After solving a problem, we know a lot about it. The problem is, the people who we are communicating the solution to, don't know nearly as much. This is where the "Curse of Knowledge" comes in. What we already know, we have to get across to others. The problem is that what we think is important may not matter unless you can get others to buy in to your solution. The book provides the recipe for SUCCESs. <br /><br />www.madetostick.com is their website.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-52500197054337984092009-08-31T18:01:00.000-07:002009-08-31T18:20:30.393-07:00Multi-tasking, Learning and Phone ConferencesMy company is getting more distributed. Workers on a project (problem) located at opposite ends of the country and even overseas. For that reason, we are having increasingly frequent phone conferences. They're great for touching base frequently without having to hop on a plane but I have some doubts about how effective these meetings really are.<br /><br />My earlier post about multi-tasking cites evidence that multi-tasking is a misnomer and yet these phone conferences are a invitation to do so. One ear on the phone, sending an e-mail and perhaps even in IM or working on a document is probably pretty standard behavior for participants in a phone conference. Frequently someone is asked a question and their response is "Pardon, please repeat the question." Their attention was elsewhere.<br /><br />In the chapter 9 of his book <a href="http://www.brainrules.net/" target="_blank">Brain Rules</a>, John Medina reviews studies which show that optimal learning is when multiple senses are involved . In phone conferences, we only have one of our senses involved. When you're in a meeting, you're learning, unless of course you are doing all the talking. You're learning what others know, what you have to work on, what they're working on. <br /><br />The phone conference is a less than ideal learning situation. I wonder if there are any studies on the efficiency of face-to-face meetings versus phone only and phone and visuals. I wonder where the break-even point is for the travel costs versus the wasted time in the meetings.<br /><br />Some suggestions for your next phone conference.<br /><ul><li>Send an agenda out beforehand so everyone is prepared to <span style="font-style: italic;">learn </span>about the topics.</li><li>Use some sort of desktop sharing program so everyone is seeing the same information.</li><li>Send out minutes along with any visuals after the meeting is over so everyone can review the outcomes. (Another chance to learn what was discussed).<br /></li><li>If you're a participant. Pay attention. It may seem like you're more productive when sending IMs, EMs, but every time you ask for something to be repeated you're wasting x number of other people's time.</li></ul>Modern technology has made many things more efficient, but our brains are still "primitive". We learn best by incorporating multiple senses and reviewing the information multiple times.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0tag:blogger.com,1999:blog-4544803008461181295.post-60975156071538036982009-08-28T18:37:00.001-07:002009-08-28T18:55:03.715-07:00Being Good EnoughThis month, Wired magazine has an <a href="http://www.wired.com/gadgets/miscellaneous/magazine/17-09/ff_goodenough", target = "_blank">article </a>about products that are good enough to do the job but not great. The point of the article is that this is how these products can creep up on the leaders in the field until eventually the are capable of surpassing them. <br /><br />The same applies to problem solutions. Often we are perfectionists, trying to anticipate every possible angle before implementing the solution. Sometimes this can delay implementation of a solution and result in lost opportunities. Often (except when safety is involved) getting a partial solution in place quickly is more important than addressing all the issues beforehand. You can then evaluate what the weaknesses are under operation and utilize an iterative process to optimize the system. Your supporting structures (management of change, document creation, document control, etc.) need to be efficient enough so that they aren't a drag on the process.<br /><br />If your support functions are more taxing to complete than the solution itself then something is wrong. Often Quality organizations become enamored with lots of checks and balances and the whole process gets bogged down. Often these people aren't users of the process but only enforcers. If you start thinking to yourself that you know how to do something but don't want to cut through all the red tape to get it implemented, then something is seriously wrong. Both because good ideas may not get implemented and because people are tempted to take shortcuts without submitting the ideas to the proper review process. This can lead to unintended consequences.<br /><br />Even our best laid plans can go awry. One needs to balance the desire for a "right the first time" solution with the inevitable refining process that occurs anytime you try something new. Continuous improvement works best when it is continuous. If it proceeds in fits and starts, then often it won't re-start.mattjhttp://www.blogger.com/profile/05532899509096532143noreply@blogger.com0