The Community Blog for Business Analysts

In Part I of this series, I introduced the concept that, from the perspective of complexity, everything exists within a system. In Part II, I outlined a three-tiered framework of effects-based thinking (EBT) and planning that is critical to understanding how change propagates throughout these complex systems - the organizations, markets and communi...

Information Systems Users don't know what they want... So, don't ask them what they want: and definitely don't write some software and then say "how's this look?". On the other hand, don't have someone spend weeks talking to various people about what they want ( and not get to talk to other people ), write it all down and deliver a document, sayin...

In 'Effects-Based Thinking - Part I', the definition of effects-based thinking, or EBT, was established as an approach to strategic planning which contributes to long-lasting organizational impacts. Expanding on this concept, let's look at what the differences between strategic planning with EBT and simply tracking progress with metrics are. Many ...

Are we looking at it all wrong? Do you ever get the feeling that you are seeing something very different than the other guy? I don’t just mean the glass half full/empty outlook on life, but fundamentally are we looking at things the wrong way? I sometimes get that feeling when dealing with projects that involve processes, and all my projects are...

As the name implies, effects-based thinking (EBT) is an approach to strategic planning and decision making where the effects of specific actions are assessed, not in a narrowly defined and time-limited way, but through a perspective that is sensitive to broad-ranging and lasting impacts. Effects-based thinking is the opposite of short-sightedness o...

BA: “They didn’t pitch for my workshop. Again.” Mentor: “You must be mortified.” BA: “Seriously, they come up with these lame excuses: they don’t understand that computer stuff, they’re too busy, they think it’s a waste of time. One even told me to get it done and let him have a look when I’m finished. How the hell must I fathom the requirements ...

If you work in new product development or have participated in maintenance projects, then most likely you have used either the focus group or the brainstorming technique. The brainstorming technique is used to produce ideas and increase creativity. For example, after you’ve defined your problem and are looking for the different solution options, yo...

Requirements gathering is an essential part of any project and project management. Understanding fully what a project will deliver is critical to its success. This may sound like common sense, but surprisingly it's an area that is often given far too little attention. Many projects start with the barest headline list of requirements, only to find ...

I've been working with a company now for a little over a year as a contract business analyst and I think it's fair to say that they are still evolving their understanding over how to effectively utilise BA's like myself. So far, i've been fairly successful in deploying methodologies, BA tools and techniques, but i...

I have been delivering projects successfully since the early 80s. Back then, we didn't have business rules, we had formal logical data models, entity life histories, data constraints, and data flow diagrams. In general, all the necessary business constraints got captured properly and implemented. Some of these deliveries actually passed acceptance ...