Backstory - Understanding cause and causality

Just like every great hero has a great backstory (okay, some not so happy, but...that applies here, too), every project has an initiator. A spark that sets off a series of complex events leading to a greater outcome, a better future, a broader understanding, or at least a slightly more optimized process flow.

Superman was sent to earth and understood his potential for good. Spider-Man had to learn the hard way that with great power comes great responsibility. Booster Gold...well, he's not a great example, so we'll set him aside.

In a very similar fashion, projects have starting points born of necessity for not just one, but many. Data intergrity. Process optimization. Budget optimization (hey, gotta happen, too; but the right way!). Partner process training. New platform launch. Hardware installation. Employee training overhaul. I can go on and on, and so can you, I'm sure. The point is, these things impact a WHOLE lot of people. So what a responsibility we all have to ensure that the correct path is chosen, in order to come up with the desired results.

Now, I'm once again stating obvious points. Just setting up the main idea: you can't go where you're headed if you don't know where you're coming from. Understanding the underlying need for the project is key. You can't hope to train people if you don't know what they'll use their knowledge for. You can't set up a security system if you don't know how tight it needs to be. You can't install a server without knowing the infrastructure it's going into.

I am very, VERY serious. Too often have I seen people jump into ongoing projects and starting to take on tasks without any clear vision of where they were in the bigger picture and why they were doing what they were doing, which inevitably lead to them stepping on parallel teams' toes or missing the mark by just enough to have to redo a lot of the work.

Whether you're starting a new project or stepping into one already running, please make sure you take the history. You can't build a heroic end without a tragic backstory (of sorts).

At the same time, you need to know, throughout the project, what's going to impact which part of the project at which time. You know why you're doing the project, but now you need to know which steps to take to...I'm going into too much detail, aren't I? Look, if you're a bit of a comic book nerd, like I am, you'll know that there are other worlds in which Superman didn't do the right thing. Spider-Man took it a bit too far etc. There were steps they took in those worlds that no longer lead to the heroes we know, but to the complete opposite.

Be inquisitive, ask around, talk to your peers in parallel organizations, find out as much background as possible so when venturing forth, you have enough information to make informed decisions and know who to turn to in case of need (and who might turn to you, as well.)

I realize I've gotten so deep into the superhero metaphor, that I completely forgot to use a D&D analogous situation. How's about...hmmm: your character's background determines their world view and how they interact with the people around him, maybe even other characters in the adventuring party. It's what leads them to make certain choices as they grow in level. If you're good, cool, experienced, and well-meaning (please be well-meaning), then the choices you make will lead to a great hero that saves the world.

Unless your target is world domination, in which case...you know...different kind of project, different targets, different milestones, different risks, but still manageable. You do you!

Cheers!

Calin.