What Is The Output Of Your Work?
A few years ago, while in the middle of a big product release, I turned to a co-worker and asked them: What is the output of your work?
This sounds like a silly question, but I found it to be enlightening to reflect on. Here we were, stressed out about making something. However, what we were really doing was producing the documentation, the knowledge, and the confidence in the product we were making. It is easy to get lost in the idea that what you produce is the gizmo, gadget, or the most tactile result of your actions. In some ways it is tempting to think that if you paint you produce a painting; if you write music you produce a song; if you write code it is the website or demo that is the output of your work. On reflection I found that while the direct goal is often one output of your work, in many ways is more a side-effect. In this view the main output is the information, experience, and documentation that is created by the process of doing the work.
It is being process-oriented. In some ways this reminds me of the following excerpt from the Bhagavad Gita:
You have a right to perform your prescribed duties, but you are not entitled to the fruits of your actions. Never consider yourself to be the cause of the results of your activities, nor be attached to inaction. — Bhagavad Gita: Chapter 2, Verse 47
If you organize your work to sit on a framework of systems that can capture knowledge (and digest that into wisdom and principles), then you do the one thing you can do, which is engage in action. If you focus only on the final goal, and reward, you might miss the experience of doing the work. Maybe even miscalculate your efforts by becoming results oriented. By doing this you might neglect the experience of doing the work, to improve in the future, and share what you have learned with others. Then even if you do not produce the result you originally intended to you have still continued to tend to the process by which you engage creatively with the world.
If you are an engineer in an organization it is your duty not just to produce results, but also to produce a knowledge base, on top of which more can be done tomorrow than could have been done yesterday. Without these raw materials that are produced through the creative process then you may leave with a painting, but know new knowledge! And with no new knowledge we cannot reflect to glean some wisdom from our experiences.
It would be misleading to say that this is so cut and dry. If you now focus only on process, then maybe you wont ever make anything. Sometimes there are great pressures placed on us to produce output so that we can continue. These moments, maybe, have the most to teach us about process orientation. In technology development, it is my belief that these moments create technical debt, but also create great leaps forward. Once again, maybe the technical debt, the messiness, the understanding of the mistakes made is the truly valuable output of your work.
It has been my experience that it is tempting to look back at this as a failure of procedure, or a bad thing. However, the actions earned you a spot at the table, the right to play, and now you have information available! Information can be processed to knowledge, and maybe someday become organizational wisdom!
So I ask you to occasionally reflect on your work, and ask: What is the output of my work?
And with a deep breath find the answer for yourself, allowing yourself to re-engage with the true nature of your actions.