Having spent the last two weeks thinking very little about business analysis or other work, I'm finding it rather challenging to get my head back in the game. This holiday I spent a lot of time on Google+, setting up a community (called +Business Analysis) and connecting my old blog to my new profile. This has rekindled my desire to blog, and regularly. To start things off, here are a few of the things I've been working on.
Yesterday I finished a revision of an article for the upcoming "Best Practices for Better Business Analysis" peer-reviewed publication starting up this month. It's the longer (and better) version of an article in the December 2012 BA Connection Newsletter (both are called CARRDs: Constraints, Assumptions, Risks, Requirements, and Dependencies).
The next article in the Business Analysis Core Concepts Model (BACCM) series is called "Needs and Solutions, Requirements and Designs" and should be out this week (no link yet) in the January 2013 issue of BA Connection.
While working on that piece, I had a set of conversations that seemed philosophical, but were really quite practical. The topic was 'objective vs. subjective reality'. Humans have opinions and perceptions and beliefs and experiences. If something exists independent of those factors, it's objectively real. If something exists because of those factors, it's subjectively real. Weather and love are both real, but they're in different categories.
The thing that knocked me for a loop - and has intense, practical implications - is that the things we call 'objectives' are not objective. Sure, we state them with a variety of objective characteristics (as in a SMART objective that is Specific, Measurable, Attainable, Relevant, and Time-bounded) - but the fundamental fact is that the objective has a necessary subjective component that we ignore: value.
All that to say the February BACCM article will be called 'Subjective Objectives'. Coming soon!