Tips for Problem Solvers

I saw this great post on LinkedIn earlier this week.

My job titles have varied wildly, but generally I have been hired to be “the technology person” or “the innovative person” at my places of employment. This has meant that a significant portion of my time is not doing “technology” or “innovation” but rather explaining to people that they don’t need what they think they do.

Sarah Glassmeyer: Crushing Your Hopes and Dreams Since 2008.

From digital repositories to apps to dashboards to “data”, people get it in their head that they need a certain tool, either because it will magically make life easier or, worse in my opinion, everyone else is getting it so they need to keep up with the Jones.

Someone gives a talk at a conference on how X is the next big thing and then administrators are like:

Let’s ignore how often the proponents of technology have a financial stake in it succeeding. Oh, whoops, that was the voice outside my head.

So, should you find yourself minding your business and a person who may not sign your paycheck but has the power to make your work life real bad comes up to you and says “we need x”, definitely start with “What is the problem you are trying to solve?” It sounds simple but you’d be amazed at how many people really can’t articulate an answer.

So, here’s my roadmap for navigating this type of situation and some questions to ask. This is not a full project planning roadmap, this is my “what I ask over cup of coffee to see if it’s actually gonna be A Thing.”

1. What problem are you trying to solve?

2. Who’s idea was it to get this tool?

3. Who controls budget for project?

4. Who will actually use tool?

5. Have they been consulted?

6. How do they deal with issue now?

7. Have you talked to any vendors?

Two, three and four and usually not the same people and you’d be amazed at how rarely five happens. You know how people are excited when the Publishers Clearinghouse people show up at their door with a big check? It turns out that doesn’t happen when you show up with new piece of technology. I like to check seven just to get an idea of how rosy a view they may have about implementation.

Post Q&A things to emphasize before actually beginning project:

1. The actual solution to problem may not be an addition of technology. It’s been said 1000 times, but adding technology to a terrible process just makes the terrible process be more efficiently terrible.

2. Who is going to be my point person that will be my liaison to your organization?

3. Before investing time and energy on creating this solution, what is the plan for maintaining it after I exit the process?

I don’t have a PMP or LMP after my name, but I do have a trail of failed projects and mistakes where I picked this up. All the good intentions and even all the money in the world won’t mean a thing if people aren’t prepared to do the work.