Technical Problem Solving 35 The same is true of Patricia Wynjenek. Although at some time she may be able to recommend new social programs on the basis of what she has found out about the economic survival strategies of the people she was studying, she is not in a position to implement them. Others in public or private agencies would be responsible for implementing the solutions that Patricia recommends. But again, Patricia's understanding of what implementation involves will make her recommendations more specific and therefore more likely to be carried out effectively. Conclusions The basics of technical problem solving--definition, research, analysis, resolution and synthesis, and implementation--are dynamic and demanding tasks. They require a commitment to under- standing and willing participation in professionalism that most who seek meaningful work in their lives are willing to make. But if they are to work--if they are to be used successfully to solve problems --they require close attention to the process involved in using them. It is not enough simply to define a problem. One then has to research the problem to find out the details of what has defined it. Once the details have been gathered, they have to be analyzed-- looked at as discrete entities, then as parts of the whole to see how they fit into a larger picture. Then the whole process needs to be resolved and synthesized--to be bound up to decide ultimately what it might mean. And, if possible, a decision must be made as to how a solution will be imple- mented. At every stage, the need for redefinition, further research, and reanalysis may present itself. Solving problems is not a clean and linear activity; it is often messy and frustrating, doubling back on itself; but once honestly and conscientiously taken on, it can render great rewards. It is not merely honorific to say that any job has been well done. The ability to say that with conviction is the ultimate test.