-
http://www.inclinedesign.info CASUDI
-
Louis P. Solomon
-
http://dr1665.com DR1665
-
Louis P. Solomon
-
http://dr1665.com DR1665
-
http://dr1665.com Brian Driggs
-
Louis P. Solomon
-
http://dr1665.com Brian Driggs
Working Credo

What’s this all about?
ADDIE aditl Be Behind the Firewall brainstorm cars Chantix collaboration community conversation curiosity distillery Do don't education FAIL fear focus friendship gearhead HowTo hustle impact integrity journalism KM leadership love meaning participation passion peace Persevere persistence process rally resilience serendipity social media Strip Mine City sustainability synthesis TWICs updates WINComments, community, collaboration.
- Brian Driggs on Community Development: A Simple Content Strategy
- rob on Community Development: A Simple Content Strategy
- rob on Chris Barba on Perspective
- In Search of Adventure on Building a New Community: Planning
- Chantix Update (Feb) on Chantix: Redux
- Brian Driggs on I Have Not Yet Begun to Write
- Brian Driggs on I Have Not Yet Begun to Write
- Sarah Arrow on I Have Not Yet Begun to Write
- Rena Tucker on I Have Not Yet Begun to Write
- Brian Driggs on I Have Not Yet Begun to Write
- Eugenio Perea on Michael Banovsky on Be
- Tim Kastelle on I Have Not Yet Begun to Write
- Brian Driggs on Social Networking: It’s About People
- Kim Schuenman on Social Networking: It’s About People
- Brian Driggs on Social Networking: It’s About People








On Problem Solving
Regardless of how you solve problems, I think it’s a good idea to keep an open mind to different ways to do so. A recent blog post I read discussed a process in which a group collaboratively considered a problem and developed a solution to resolve it. I can’t say I’m opposed to that idea at all. In fact, I’d say that would be my recommendation for just about everyone, but I’d offer one caveat to that. We shouldn’t feel that this is the way to solve every problem. If you can see the solution on your own and it’s within your power to make the change, then do so without delay. Even if you fail, you will learn from the experience and be better prepared for the future.
In the last few days, problem solving seems to have been a recurring theme. It sort of snuck up on me. At the office, we’ve been talking about the ADDIE model and how it can improve our processes within the department and organization. ADDIE stands for Analyze, Design, Develop, Implement, Evaluate. I’d been chalking this up to a methodology for the workplace which could have uses elsewhere, but it was mostly a work term for me. Then I had a brief conversation on Twitter with @CASUDI last night about problem solving processes. This is where I found a fog between collaborative and individual problem solving styles.
A little bit about me in this regard, I tend to just pull solutions out of thin air. I couldn’t diagram a sentence to save my life (always hated that part of English class with a passion), but I like to think I have a pretty good idea of when a sentence is written good. (Pun intended.) I don’t know. It’s like I subconsciously analyze the problem and feel the solution. When questioned on these solutions, more often than not, I am able to go back and relate why it works. It’s not always the best way to do things, but I like to think it’s part of a learning curve. More often than not, things seem to work out. Then again, maybe I’m just talking outta my ass. Plenty of people will tell you I’m good at that too.
It’s those foggy issues that appeal to me the most. When I see an obvious problem, I generally see an obvious solution. If the solution leads to side effects that need addressed, they are addressed and we move on. Problem – solve – problem – solve – problem – solve – and so on. When the issue is foggy, on the other hand, that’s when I get excited. Now there’s incentive to tap friends and colleagues to collaborate on solving that issue. I’ll still tend to pull ideas out of thin air, but collaboration allows my peers in the decision making process to shoot them down. It’s trial and error before implementation. Guess you could say I work the ADDEI model when working with others.
More important than the exact steps to solve problems, in my opinion, is knowing when to collaborate and whom to collaborate with on the solutions. If you can personally consider all the options and are willing (and able) to handle the outcome if it’s less than desirable, then I say go for it. If you are wrong, you will get a valuable learning experience, hopefully sharpening the sword, which should make you more proactive than reactive overall. If you have any doubts, however, collaborate with people you trust. These people shouldn’t necessarily agree with you on everything. In fact, you probably want people to poke holes in your ideas so you can modify your plan accordingly. Trust doesn’t mean “agrees with me on everything,” but rather, “offers me alternatives because they genuinely want to help me.”
It’s also important to have a strong sense of direction. How lost can you get if you have a compass and know which direction you’re heading? Besides, life’s a journey – not a destination, right? Given that mindset, since there is no final destination, there’s no way to plan out all the highway exits and street corners.
Where are we going? That way.
How are we getting there? By sharing our knowledge and ideas with others.
In the glovebox: