Linking the Abstract to the Concrete: Make Your Business Case Count!
One of the most persistent mistakes made by consultants and mid-level to senior leadership professionals is an inability to link abstract theoretical organizational interventions to concrete business activity and functions. In working as a leadership and organizational development consultant and business practitioner for six years, and an HR professional for nearly 20 years, I have witnessed this first hand on more occasion than I care to admit.
Allow me to present a story: Once in a history not to distant, I was a supporting initiative project team leader and change management team member working on a fairly complex change management initiative. This robust and aggressive inititiative involved the entire organization, its business units, core business functions, staff support functions, and information systems. Thus, in the organizational textbook sense of change management, it met the criteria of being both complex and essential to maintaining the advantage in the industry of which it was a part.
The concept was Appreciative Inquiry (AI) and my core role during the exploration stages was to unearth practical utility prior to implementation stages of supporting initiative projects. The organizational leadership, rightfully, in my opinion, did not believe in abstract concepts unless empirical evidence supported cost and effort; in other words, could a quantitative and qualatative business case be built around workforce actions built into the operational and functional actions of employees.
The resistance to the concept initially came from my inability to link AI (in this case) into observable actions. And here is an important point: Professionals with whom I work usually have very little issue or challenge in developing and linking abstract entities and theoretical management concepts during the strategy planning and visioning phases. However, there is a tendency to “fake it,” or at least hope someone will not notice when it comes to relating the concept to observable actions that can be empirically measured and assessed. As it related to my experience, the impression formed that AI was another fuzzy management concept with no practical utility. It became a concept in which one accentuated the positive to perhaps reach states of the ideal working environment. Bright (2009) states that a one-sided reception of AI hinders its organizational employment potential stating, “I am concerned that an understanding of Appreciate Inquiry as simply ‘a focus on the positive’ undermines its full potential to create sustainable change in organizations . . . researchers have helped us understand that organizations are most vibrant and alive when they embrace the tensions of the human condition” (p. 2). My point quoting bring is that this can apply to most abstract organizational intervention (i.e. emotional intelligence, cognitive diversity, etc.)
Specific to my case, I felt that AI was more than just emotional and abstract strategic entity and intervention merely to be integrated with selected management methodologies such as performance management and its accompanying tools. As related to AI, Bright (2009) points out the operational components of AI stating that AI “. . . refers to an increase in the value of capital. Operational appreciation usually refers to the value of financial assets.” This was my intuitive “aha” moment that allowed the concept to gain traction. When I approached AI from both connotations (the philosophical and operational), I not only received the necessary buy-in, I received support in the infamous stakeholder meetings in which every dollar toward project and their teams has to be accounted. To put this in a tangible perspective, what I did was capture the ideal in theory and the practical in “real world” and linked those to the core functions, tasks, and outcomes to be achieved by the workforce – related to readiness, brand equity, profitability, and organizational citizenship. As a result (and understand I am compressing for space sake), the mind-set shifted from “we are broken” to “we have done this before and we can do it again . . . even better . . . within the context we need to move forward.” Again, this was intuitive at the time and have I had the benefit of additional experience and sound research, the learning curve may have not been so steep.
The lesson here: Abstract entities and notions must make sense from a business and organizational perspective. My personal experiences tell me that until you link the concept to the concrete (what is real for the stakeholders, clients, workforce, etc.), organizational interventions, especially among senior level leaders, are merely theoretical rhetoric, which captivate scholars and consultants at the moment. It is important to know the business and the concept.
Further Reading/References:
Bright, D. (2009). Appreciative inquiry and positive organizational scholarship: A philosophy of practice for turbulent times. OD Practitioner, 41(2), 2-7.
Comment » | HR Communication, Leadership, Strategic HR, change management





