Today I want to talk about drive. What does drive have to do with a business analyst? Everything. It’s ultimately what makes the difference between a successful business analyst and an ordinary one.
The first thing we have to do is define what drive is. I believe that drive is that hidden motivator that makes us keep things moving when things aren’t going smoothly. It’s what makes us do what it takes to get the job done.
So how does drive help a business analyst? Many times, the business analyst does more than gather requirements or provide expertise. The business analyst often has to play other roles such as project manager or quality assurance tester. All projects have timelines. All projects have to have a leader. Most projects have delays or hiccups. It’s often the business analyst that keeps things moving.
So how does that happen? Well, like the old saying goes “when the going gets tough, the tough get going.” The great business analyst, in addition to continuing to ask questions and learn what is needed by the business, begins to work on a project plan, continues creating the requirements documentation, starts working on test plans or test scripts, organizing test data, etc…
Just because a project has slowed down or stalled, doesn’t mean you should forget about. I’ve seen too many projects get stalled only to rise up again with an even more accelerated time frame. When that happens, the information that you created will be invaluable and will make you look like a genius.