I did not know Steve Jobs, Dennis Ritchie, or Edgar M. Villchur

Tyne Cot Cemetery (Ypres)- Ieper Belgium

I did not know Steve Jobs, Dennis Ritchie or Edgar M. Villchur, or the 500,000 soldiers who died in Ypres (Ieper) Belgium in the trenches of  World War 1. Last week on holiday, reflecting on their respective work and passing away, then visiting the In Flanders Fields Museum and Tyne Cot Cemetery outside Ypres (Ieper) Belgium. I felt overwhelmed by the In Flanders Fields Museum and Tyne Cot Cemetery respective testimony. The shear numbers who died and  pointlessness of trench warfare, the leadership, story and narrative that lead to these deaths and suffering was mind boggling.

This visit marked me at many levels, and reminded me, that each of us are impacted by events, histories,relationships and connections, that give us a scaffold to build our own narrative and vision. To me Steve Jobs, Dennis Ritchie, Edgar M. Villchur, and the soldiers of Ypres (Ieper) Belgium put a mark in very different ways on my understanding of the world and contributed towards my own narrative.

Steve Jobs’ desktops, laptops, i devices, , and iTunes has always been part of my personal and professional media life, at work, home, … a fan, and appreciative user. Dennis Ritchie who brought to the digital world, we live and work in daily: C programming language and co-developed the Unix operating system. Edgar M. Villchur’s vision plays a big role in my adult life : the Loudspeaker. He invented an acoustic suspension woofer producing the loudspeaker as many of us have in our homes, car and ears:)

Each had a unique narrative tied to their ideas and vision. Their respective narratives transformed into concrete outcomes that changed the way we function in our world. The narrative built on a passion and a clear belief in the outcome where they wanted to go. Maybe not always clearly defined to others or all planned out in their own heads but this narrative drove the conversations, work,  time, creativity, thoughts, and collaboration that made their ideas a reality.

As for many of us who have a passion for what we do, our narrative and story is constructed through events relationships, collaborations and belief based on experiences. The key to the success of Steve Jobs, Dennis Ritchie or Edgar M. Villchur,  narratives was they each transformed it into some thing concrete that was operationalized to significantly impact people and change the way we do things.

This transition from idea to reality is the most complicated and challenging aspect of building ones own narrative and ensuring it becomes reality. Ideas can be generated, conceptualized, discussed, debated, and dreamed up.  The delicate process of making an organizational narrative engaging to others so they adopt it as part of their own narrative is in my opinion the true art of visioning.  The key is that there needs to be a strong buy in by all players associated or connected to the narrative even if translated or interpreted through a different lens. To often I witness rich and engaging visions, but so often the operationalization piece is missing. This is due to the  narrative being lost in the translation before it becomes others own narrative in any organization. Without people in an organization internalizing the visionaries narrative within their framework of understanding little will become concrete and have an impact on others . Once you have this common narrative throughout an organization the stage is set for the intricate collaborative mechanism of choreographing and operationalizing a shift that creates change with ever lasting impact. Each of these men did!  Do you have an i in one of your devices, using Unix and listening to it through a set of speakers………..What is your narrative?

John@beyonddigital.org

organizational shrapnel

This post is dedicated to Joshua R. and Andrew H., thank you for your conversations and mentorings…

…as with any end to a international school year there comes moments of reflection and looking back that generate ideas and new perspectives. This year has been a challenging one on many levels due to a host of odd circumstances and situations in my department and school that effected us all in the IT Department, and required the team to face up to serious challenges. We all pulled together, and hats of to the team for their outstanding capacity to deal with everything that came to us. This has had me thinking about something I like to call “organizational shrapnel” things that fly in your face unannounced from corners you would not expect things to come from. Sometimes I even refer to these as “drive by shootings” were suddenly you are confronted with a situation unexpected and most often you are not prepared to deal with, but react and deal with in the best of your own ability.

Organizational Shrapnel is a state which generates a lot of inefficiencies, frustrations, errors, in-competencies, and slowdowns in accomplishing tasks in an organization. It is the event, moment, action or process where people look around with some confusion and try to point fingers and there is no clear evidence or concrete event that you can associate to the inefficiencies, frustrations, errors, in-competencies, and slowdowns.

Why should this be an issue? I believe that organizational shrapnel and the level of it in an organization can make or break a good team, group or organization. I believe that when groups/organization engage in a task or project, for the objective to be met you need to be able to trust and know that the different players are all going to accomplish their respective tasks, and that the framework of resources supports accomplishing the task, project or action.

This process of teams collaborating and accomplishing a task together in any institution is complicated and quite complex, we all experience this and it is no surprise to most of us. I feel if organizations, and teams can better understand the causes of organizational shrapnel and address the road blocks this tends to set  the stage for a more effective and smooth collaboration of a groups within any organization.

So what are examples of organizational shrapnel? These are broad in scope, and come in all shapes and shades.

  • A team works together and defines group agreements, but a member continually does not abide by these.
  • A decision is made and agreed upon, but there is no clear implementation plan, or process for feedback and evaluation.
  • A process or procedure is implemented within the organization, some stakeholder decide to follow it, others decide to not use it and use an alternative in isolation of the rest of the organization.
  • A collaborative group works together, but all the actions and follow through are continually done by a few, and others play lip service to the work but are not participating actively and tend to block movement in the meeting setting
  • An event, or task is organized and one of the stakeholders makes an error but does not report it, or share this out so others can support in correcting this.
  • Not following through on things
  • Looking at a situation within one perspective, and expecting others to follow through

…and many more, generally the pattern is that organizational shrapnel are small things which fall through, not completed tasks/steps, ignored agreements, tasks done inadequately, or where there is a lack motivation, drive by the players involved in completing the collaboration or task.

The frustration if organizational shrapnel becomes a habit and people accommodate to it, it can quickly become part of the organization’s culture and norms. The reality is all organization have a level of this, and the challenge is what environments and understandings can be shared to decrease it’s presence in any group or organization.

Organization, groups and teams who have a high capacity to understand and concretely deal with their organizational shrapnel create an environment where there is a greater motivation by the stakeholders of the organization which results in a sharp increase in creative flow generating innovation in moving forward.

John@beyonddigital.org