Tag Archives: Organizational Dynamics

What Did I Say I Did?

Biz Card

You Read it on the Internet, so it Must be True!

Anyone who knows me, knows I am quite the stickler for clarity and correctness in communication. I have proudly held myself out as a Senior Inspector in the U.S. Grammar Police, as evidenced by this card I created only halfway in jest. Actually, the card’s creation (I shared the process publicly) led to a couple of paid editing gigs. I’ve also been called a Grammar Nazi, which has caused me to momentarily flash a slightly sheepish smile, accompanied by a sparklingly demure blush.

Recently, I began a new engagement with a company I’ve wanted to work with for some time, Quantellia, LLC. As of the beginning of the year, I am what they call a referral partner. As such, I am contracted to Quantellia to sell their product, World Modeler™, and their services, which include training, workshops, etc. designed to help organizations make better decisions. In learning about my new venture, I have come across a few phrases that are similar, yet different enough to cause me to dig a little deeper in search of clarity as to their meaning. I want to very briefly share my understanding of the meaning of four separate phrases, each of which begins with the word “decision”.

At first, I thought one of the terms was kind of a catch-all; an umbrella term that encompassed the others. However, I no longer believe that to be the case, at least not fully. Keep in mind, all four of these phrases are relevant to what it is Quantellia and I are doing. At the same time, my understanding is quite likely imperfect and incomplete. As I gain a foothold in the discipline, and become more proficient, I have no doubt my definitions and my understanding will need refinement. 

Decision Science – at first I thought this term was one into which the others neatly folded. However, having done a bit of research, I can no longer say that’s the case. As I currently understand it, Decision Science concerns itself not so much with the process of making business decisions, but with the psychology of making any kind of decision. In other words, why do people make the decisions they do; what are the factors they take into consideration; how do they weigh them; how emotional are people in reaching decisions, etc.

Originally constituted in late 1968 as the American Institute for Decision Sciences, and later named the Decision Sciences Institute, this organization had its first annual meeting on October 30 – 31, 1969 in New Orleans. If interested, here’s a history of the organization written in July of 1989 by the then President, Bernard W. Taylor III. According to Wikipedia, the Institute is a “professional association of university professors, graduate students, and practitioners whose interest lies in the application of quantitative and qualitative research to the decision problems of individuals, organizations, and society. Many of the members of this academic organization are faculty members in business schools.”

It seems that Decision Science is a relatively new discipline. This conclusion is backed up by the history of its presence in some of the Universities and Colleges in the United States. For instance, Carnegie Mellon University’s Department of Social and Decision Sciences finds its roots in 1976, as part of what is now the Marianna Brown Dietrich College of Humanities and Social Sciences.” The Harvard Decision Science Laboratory opened its doors much more recently. According to their website, they’ve only been around since January of 2009. I couldn’t find the date George Washington University’s Business School’s Department of Decision Sciences opened its doors, but my hunch is it was sometime in the last decade, at most. The Columbia Business School’s Center for Decision Sciences, formerly part of the Institute for Social and Economic Research and Policy, appears to be fairly young as a separate discipline as well.

Decision Modeling – Although at best an inexact science, decision modeling can be a highly effective tool in helping an organization better predict the outcomes of its decisions. This is made more likely if the model is comprehensive, based on not merely data and analytics but also the knowledge of the people involved in the organization for which the decision is being made, and if the model is iterative and capable of incorporating newly discovered information and relationships. Furthermore, the structure of the model becomes more and more effective as it accurately models the complex relationships it seeks to help understand. World Modeler™ is capable, despite it’s seemingly simple interface, of modeling highly complex relationships. I’ll post more in the future about its capabilities, including embedding some excellent videos showing what it can do.

Decision Engineering – This is a term I don’t believe we are using any longer to explain what Quantellia does. Frankly, as someone who spent over two decades working with aerospace engineers and rocket scientists (quite literally, on the Space Shuttle Main Engine, Delta, and Atlas engine programs), I’m kind of partial to engineering. I can, however, understand how it may sound a bit intimidating or dweeby to people without my background, so I won’t dwell on it here.

Decision IntelligenceDecision Intelligence – This is the term Quantellia now uses to describe what it is we do. NB – The term is not “Decision Analytics”; there’s a reason for this. Perhaps it is best understood when one looks at a part of how decision modeling is accomplished. Part of the raw material available today for making decisions is what we call “big data”. There’s an awful lot of attention being paid to the field of predictive analytics, which uses big data as its raw material. We at Quantellia prefer the term predictive intelligence. This is because predictive analytics uses past performance (data) to project trends into the future. We like to think we take the concept a bit further.

While we believe analytics are useful and important, they lack the dimensions of human knowledge and understanding that can more completely predict how the past will play out in the future. A subtle distinction? Perhaps, but I find it a valuable one. Unless we’re talking about the future activity of a machine designed to perform a very limited set of instructions or actions, our activities involve human understanding, emotion, and interpretation. There are times when these attributes can dramatically change the course of an organizational effort, rendering previous decisions moot or, at best, only partially useful or correct.

By providing a method whereby human understanding, intuition, and wisdom can be incorporated into the decision model itself, we believe we can more intelligently predict the future. We are well aware there is no such thing as infallibility. However, we also know the more useful and actionable information and knowledge we have available to understand what has happened − and is likely to happen − the better our decisions will be.


 

Mild Disclaimer – I hope I didn’t rattle anyone’s cages too much with these definitions/explanations. They represent my current thinking and, being somewhat of a newbie to the science/craft of decision making as a discipline, my understanding is necessarily incomplete and in a state of flux. Nonetheless, this is a first attempt at explaining some of the concepts that are informing my work with Quantellia and World Modeler™. Consider it an ongoing process.

At the same time, I would like to make it clear that Quantellia has been doing this for approximately eight years and has a track record of helping organizations both large and small to make decisions and manage programs successfully. Dr. Lorien Pratt, co-founder and Chief Scientist, as well as her team, know their stuff and are the biggest part of my team. We are looking for people who have “wicked problems” they need to solve; people who are facing highly complex decisions involving lots of time and money, and for whom the wrong decision could be very costly. If you fit that description, or know of someone who does, you could do a lot worse than contact us for an initial discussion of your needs. We begin with the end in mind and believe we can help. Only by understanding what it is you face can we determine whether or not that’s possible.


The Hell It’s Not About The Tools!

Hand Axes

What Would Lizzie Borden Do?

I had lunch a while back with a former colleague from Pratt & Whitney Rocketdyne. He is also a fellow cohort member from my Masters in KM program, from which we both graduated in late 2009. We have worked together extensively. After eating we were discussing the situation at my former (and his current) place of employment, which is a bit unclear at this point.

As I shared my thoughts about the value (as I see it) of using social media to increase the organization’s capabilities (you know, the innovative, collaborative, communicative ones), he said something he had said to me over and over while I was still a colleague . . . “It’s not about the tools!”

Now, essentially I agree with him – at least to a point. Tools are, by themselves, absolutely useless unless they’re used to get things done in the manner for which they were designed. Even better, if you can figure out how to use them creatively they can be even more powerful. Try pounding a nail into a stud with your bare fist, though, and then tell me it’s not about the tools.

Nevertheless, this argument is valid when taken in the context of an organization where people think that throwing tools at a problem will somehow, magically I guess, solve the problem confronting them. I have personally seen this happen quite a bit and, in fairness to my friend, it did seem to be a common occurrence at our place of employment.

On the other hand, we’re probably all aware of situations where the simplest of tools served an organization well in dealing with a particularly difficult situation. This can only happen, I think, when the people confronting the situation are open and honest about what they’re facing and how it’s affecting the processes and people who are tasked with dealing with it.

This means they have to be able to think both critically and creatively. Too often people get to thinking in predictable ways and they pigeonhole the problem, thereby confining their possible solutions to the things they’re familiar with and have previous knowledge of. This usually leads to failure.

The thing about tools, though, is that they frequently give us the ability to use a bit of lateral – or even sideways – thinking. In the case of social tools such as Jive or Socialcast or Yammer, we’re also given the possibility of working together and sharing our information and knowledge in ways not previously possible.

A perfect example of how not to do it is the way in which the company I used to work at shared their knowledge of rocket engine design and manufacture. It was always the case that younger Engineers would send email requests to their older counterparts, requesting information on design intent or material properties or manufacturing techniques, etc. The older colleague might spend days researching and crafting an answer, which would then be sent back to the requester in an email.

The problem with this was that access to all this wonderfully useful information was now confined to the two (sometimes a few more, depending on who was included initially) people engaged in the conversation. Usually, within a short while the information and knowledge so thoroughly and carefully created was lost; frequently even to the original person asking the question. This was because there was no useful method by which email could be easily searched.

Nowadays we can do much better. We have tools, applications, and systems available to us that provide functionality like instant broadcasting (micro-blogging), collaborative creation (wiki, even Google docs), and ubiquitous indexing and search. There is, in my opinion, no excuse for not taking advantage of as many of these tools as is reasonably affordable – taking into consideration the culture of an organization and its tolerance for experimentation and change. Frankly, from what I’ve experienced and from what I learn from friends and others who are engaged in community organization and leadership, there are ways to introduce, champion, and develop these kinds of tools in just about any organization.

So I would wish to characterize the use of tools just a bit differently. I would say it most definitely IS about the tools, but it’s just not entirely about the tools. Having functionality available that was not possible five or ten years ago can change things dramatically. However, it doesn’t happen overnight. It takes a conscious effort and, sometimes, dramatic changes in the culture of an organization. Nevertheless, the pain associated with change is usually ameliorated by the newfound capabilities the change brings; the possibilities of developing innovative processes and organizational structures and of increasing both the efficiency and effectiveness of those things we engage in. If anyone tells you it’s not about the tools, as if to say they aren’t important, ask them when was the last time they combed their hair with a fork!


It’s Getting Chilly, or How I’m Planning on Doing Some Cold-Calling

Well, I’ve finally decided to go out in earnest and get some clients. I don’t think I’ve mentioned much (if anything) about what I had hoped to do with my life after leaving Rocketdyne and, frankly, it was a bit amorphous in my mind for some time as well. I keep looking for ways in which the knowledge I’ve gained over the years can be put to good use for others. I’m beginning to see some fairly clear outlines of just how I might be able to do that. It isn’t all about “clients” either.

Today I met with the Principal of my youngest daughter’s school, Sycamore Elementary in Simi Valley; on Friday I am meeting with the Principal of my other daughter’s school, Vista Elementary also in Simi. I decided a while back I wanted to see if I could bring something to the table that might improve the educational system . . . some small but significant contribution I might offer that would take advantage of my Knowledge Management, Social Networking/Computing experience, as well as my overall skill set acquired from well over four decades of business experience.

Today’s meeting was a bit of serendipity, actually. I take my children to school every morning, dropping the older one off first, then dropping my youngest off on the way back home. Today I also walked the youngest in and watched her play a bit before class started. I then went into the office to talk to the Principal. My intent was to have essentially the same conversation I had with the Principal at Vista. After all, it resulted in an appointment to delve further into the issues. All that I could have asked for. I discovered today was the one day out of only a few in which she has set aside some time to have coffee and a chat with whichever parents happened to show up. Lucky for me!

Double lucky . . . the President of the PTA was there as well. She was very interested in what I suggested which, btw, was that I learn how they do “business” with an eye toward discovering ways they can take advantage of new tools, services, and techniques that might relieve them of any pain they’re experiencing. I know they’re experiencing it. You can’t be paying attention and think the schools and their ancillary organizations aren’t suffering from any number of headaches and problems which would improve the educational experience for students, teachers, parents, and administrators alike if they could be even partially solved.

So that’s what I offered to give to both schools. I have suggested I can afford to put in at least four hours a month per school and I am both willing and eager to do so. I plan on taking the same attitude to commercial and industrial establishments as well. I believe there are lots of ways in which social computing can be put to good use for small, medium, and large businesses. I also believe there are a lot of people out there who are holding themselves out as Social Media “Experts”. I am not doing that. I’m merely saying I think I can help – first and foremost – understand what kinds of problems any particular organization has that they want to address. Only then can they even think about what tool, service, process, or technique might serve to do so.

In order to drum up business that will actually make me income, I have developed my first piece of “Collateral” to leave behind after visiting the organizations I offer my services to. Anyone who is following me on Twitter, is my friend in Facebook, is connected with me through LinkedIn, reads this blog, or connects with me in any one of numerous other ways probably knows I’ve shared a few presentations I’ve given in the past – when I was still an employee of Rocketdyne. They can be found on Slideshare, here. I want to share what I’ve done in creating a brochure to leave behind after an initial conversation with a prospect. My intent is not for this brochure to introduce me, but rather to serve as a reminder of the conversation I expect to have with whoever it is I’m discussing these things with.

I know, from my years of pursuing knowledge in this field, through literally hundreds of conversations on the subject, and from following and reading the work of dozens of people whose intelligence I have nothing but the deepest respect for, that almost anyone; every process; every business; yes, even every institution – up to, and including, those of government at any level – could be improved through the intelligent application of social computing. Of course, every situation is different. The City Council here in Simi surely would neither benefit from, nor require, the same thing that might benefit the U.S. Senate, and a small restaurant surely doesn’t require the same capabilities that a large manufacturing or distribution enterprise would find helpful.

So . . . that’s my story, and I’m sticking to it. Below are the two pages of a three-fold brochure I’m going to get printed shortly and start bringing with me as I literally knock on doors. It’s not the only method I intend on using, but it gets me out of the house, and that’s a good thing. I’d be interested in any feedback those of you who might read this post have to offer. I’m a work in process. Aren’t we all?

Click on Image for Larger (Legible) Version

Click on Image for Larger (Legible) Version

P.S. – Special thanks are due to my friend Luis Suarez, who was kind enough to look over what I had done and make some very useful observations and suggestions. Thank you so much, Luis. You are one of those people whose presence I value dearly.


Companies Should Pay Attention to Former Employees

Today, my friend (I consider anyone I can have a decent, useful conversation with on Twitter a friend) Kelly Kraft (@KRCraft) posted a blog asking the question “How much and what kind of a relationship do you have with former employees?” Her experience is much different than mine, though I think her conclusions make perfect sense for any organization contemplating doing as her former org did. The question is not – in my mind and, I think, in Kelly’s – whether or not to have ongoing relationships. Rather, it is what kind of relationships, and how extensive (or intimate), will they be?

KM Through Social Media

Over eight years ago, in response to a perceived need for understanding (and locating) the depth and breadth of expertise at Rocketdyne Propulsion and Power (then a division of Boeing’s Space & Communications business unit – whew!), I did some research and found a company that provided a tool that was a predecessor of many of the social media offerings of today. In my opinion they were way ahead of their time. The tool was called AskMe Enterprise and it offered profiles, Q&A threads (including forwarding, commenting by others, feedback as to quality and efficacy), file and link uploading and sharing, etc. We later had a customization added that provided for posting Lessons Learned and, about four years ago, they added a blogging capability.

Unfortunately, the larger percentage of our workforce (especially leadership and management) adamantly refused to participate. This wasn’t unexpected, however disappointing it may have been, and we continued to use the tool and work on building acceptance by example and through its ever-growing usefulness. Many years ago, I suggested we consider finding a way to stay connected with the constant flood of experienced Engineers, and others, who were retiring or moving on to other pastures. Inasmuch as we had a history of bringing some of those people back as contractors, I thought we might be able to find an inexpensive method of remaining in contact with the majority who didn’t return.

The proposal I thought made the  most sense was to provide retirees with a secure connection to our network and, as compensation for being available for questioning within AskMe, perhaps covering the cost of their Internet connection. I don’t believe anyone took this idea seriously and it essentially died on the vine.

Intellectual Property & Communication

Now here comes Kelly, pointing out how valuable her former organization, Exact Software, has found maintaining continuous relationships with former employees can be. She also addresses the issue of what kinds of relationships make sense for different types of employees. Specifically, she notes the difference between outward-facing, highly engaged employees as opposed to somewhat sequestered, internally focused employees like many of the Engineers I worked with. She is, however, right on the mark suggesting each of them can be successfully engaged.

For instance, she points to her own experience as an Implementation Consultant for Exact and the work she did in the years since, noting there probably isn’t a great deal the enterprise needs to do to engage her. She is also, I believe, referring in part to her use of Twitter to stay in touch. My Engineer friends are not terribly likely to engage using Twitter (or blogging, or anything else that public for that matter). There are considerations of IP protection they can’t afford to ignore, as well as governmental restrictions like ITAR that, contravened, will surely bite them in the ol’ behind. This can be, and has been, quite expensive and can be done somewhat inadvertently.

Nevertheless, as Kelly points out, there are numerous ways in which an enterprise can stay in touch, and engaged, with its former employees. In Rocketdyne’s case – especially – with those employees who have retired and are not working for another company. She is also pointing out, in my opinion, that CRM (or SCRM) isn’t just for sales and marketing to dun customers with either. Social Media have many applications. Many of them are useful for engaging with an enterprise’s customers, but many are also valuable for engaging one’s own employees (current and former). The lunches and parties sound pretty cool, too.

PS – The article she credits me with was a few paragraphs of my opinion of what Hutch Carpenter (VP of Product at Spigit@bhc3) had to say at his blog, “I’m Not Actually a Geek” (which he really is, but you didn’t hear that from me).


Enterprise 2.0 Through The Eyes of a Friend

I have been a KM practitioner for over a decade, and one of the principal reasons we have given for using KM principles is the need to keep from reinventing the wheel. So, in that spirit, rather than write my impressions of the Enterprise 2.0 Black Belt Workshop here at the Enterprise 2.0 Conference in Boston, I’m merely going to point to the blog of my friend @VMaryAbraham, since she has taken copious notes and already put them online.

This will make up for the fact that I accidentally set my alarm for 6:51 pm (most of my timepieces are set to 24 hr time) and got about an hour later than I had planned, coupled with a public transport nightmare, that had me over two hours late to today’s inaugural session.

So without further ado, here’s the link to Mary’s (award-winning, I might add) blog – Above and Beyond KM – http://aboveandbeyondkm.com/2010/06/learn-from-the-e2-0-vanguard-part-3.html

P.S. – unfortunately, WordPress does not fully support the iPad yet, and publishing a blog is a bit problematic. One problem; I can’t make the URL to Mary’s blog an actual hyperlink. I’ll have to fix that as soon as I have access to a regular computer. In the meantime, if you want to read Mary’s notes you’ll have to copy and paste the URL into your browser. Sorry about that.


Has Knowledge Management Been Bad For Us?

In the world of Knowledge Management, we frequently talk about at least two different types of knowledge we deal with. The first is explicit, or codified, knowledge (stuff that’s captured and, hopefully, readily accessible in some useful form); the second is tacit, or tribal, in-the-head, “between the ears” knowledge. For most of my nearly 15 years of knowledge management practice in the aerospace business I have noted we spend an incredible amount of time, energy, and money working on the former.

At the same time we have continually asserted the vast majority of useful knowledge was the latter. I had a graphic that showed the ratio of explicit to tacit knowledge at 19 to 1, but it’s no longer accessible. So I created this one from a graphic in the public domain and added text in Photoshop. While the ratio shown here isn’t nearly what I believe reality provides, it does give a glimpse of how much remains under the surface when comparing the two types of knowledge. Actually, I found another available graphic that shows the ratio as a little greater than the one I put together, and it also lists more details of what types of knowledge comprise each of these two main categories.

For me, this is huge! In fact, where I come from we tended to use an adaptation of the Pareto principle, i.e. an 80-20 distribution, so this graphic helps make my point a fortiori. Now let me get to my point. Last Wednesday (12 May 2010), Rob Paterson published a wonderful post at the FASTforward blog entitled “Have books been bad for us?”, where he discusses the question of whether or not the web is making us stupid, as well as his belief the opposite is true. He argues that books have actually stunted our ability to innovate and create new knowledge. You really have to read the whole post, but here’s a sample I like:

But with the book comes authority. With the advent of the book, much of knowledge development stopped. Only the in group was allowed to play. What mattered was not observation. Not trial and error. Not experiment. Not sharing. But authority. Most of the accepted authority were texts that had no basis in observation or trial and error. Ptolemy, St Augustine and Galen ruled.

Rob goes on to argue, rather than making us stupid, the web is providing us with the kinds of information and knowledge connections we used to have before the book removed the more communal ways in which most of our collective knowledge was arrived at in the past.

So, here’s where I find an analogy to the work I’ve been doing for some time. Much of of what we call Knowledge Management (at least in my experience) seems to spend an inordinate amount of time and expense on dealing with the 20% (or 5%, depending on who you listen to) of an enterprise’s knowledge that is explicit. We work on organizing share drives, federating search capability, and scanning and rendering searchable (through OCR) much of our paper-based, historical information. I’m sure there are other ways in which explicit, recorded information is analyzed and organized as a function of a knowledge management activity.

But I think we’re missing the point about the real value of knowledge. If, in fact, the largest (by far) percentage of an enterprise’s useful knowledge is locked between the heads of its employees and, if (as we frequently say about tacit knowledge) much of it can’t be accessed until it’s required, why are we not spending more of our limited funds on facilitating the connection and communication, as well as the findability and collaborative capabilities of our employees?

I’m not suggesting there isn’t value to content management, smarter search capabilities, etc. I am saying, however, that I think most organizations are missing the boat by not spending more of their resources on the thing that offers to connect their people; to create organizational neural pathways that promise to be far more beneficial to the overall health of the company in terms of product innovation and design, manufacturing processes, customer relations, project management, etc. (or on and on). I am speaking of Enterprise 2.0, on which I will have a lot more to say in future posts.

The problems we face with acceptance are monumental. People in organizations that have traditionally been hierarchical and within which silos and fiefdoms emerge, turf wars and power struggles go on, and people are both kept in the dark and made afraid for their jobs hasn’t exactly set the stage for the trust required to do any kind of knowledge management effort. Nevertheless, if we’re going to participate in the struggle, we ought to be shooting for the things that are going to prove the most valuable – in both the short and the long run.

I’m a book lover myself. My reverence for books is almost stupid, actually, but I’ve worked hard on overcoming it. Unlike Rob, I no longer wonder. I see the web, and the enterprise and its internal network, as the future of our group intelligence and knowledge. What do you see?


Behind The 8-Ball . . . or Hand me The Hammer & I’ll Fix This.

Now that I’ve had a little while to work with my new iMac, I’m beginning to come down from the techno-induced stupor I’ve been in and am thinking about what this all means to me. I’ve also been thinking about what it should mean for many people who work in corporate America, where I have been laboring for the past two decades and more.

Let me explain what I’m getting at. From the first day I started working at what was then Rockwell International’s Rocketdyne division (formerly North American Rockwell), I was stuck using technology that was already a little behind the eight-ball. Back then (1987) there wasn’t much in the way of personal computers, but they were developing rapidly. I went from an IBM 8086 to an 8088 to an AT and, finally to Windows and on and on. As time wore on the level of state-of-the-artiness of the available technology I had available at work, unfortunately, fell further and further behind.

Now, this isn’t about the battle that took place between IT (formerly MIS) and Engineering for many years, and how it affected the development of the first LAN in the company (hint – it wasn’t pretty), but rather about the level of security and, perhaps, paranoia that built up over the years with respect to the use of computing resources.

Part of the problem for my line of work was the very real issue of the International Traffic in Arms Regulations (ITAR) which, sometime after we were purchased by the Boeing Company, was painfully and expensively learned after an inadvertent and ignorant violation of the Regs (another story this really isn’t about). This lesson required some education and was fairly easily addressed once understood.

I think I need to throw in a caveat here. I am not an IT person. I have absolutely no formal IT education. I am merely a business person who has worked with (mostly) micro-computers – now called PCs – for close to thirty-five years. I have participated in or led efforts in knowledge management and Enterprise 2.0 for Pratt & Whitney Rocketdyne, and I was instrumental in bringing in our first web-based social system over 7.5 years ago. I have also been the project manager for that terribly under-used application all this time as well. My point here is I may not use language that’s accurate, but I know the kinds of functionality available and I know all of it is – from a corporate point of view – there to serve the business.

What I’m concerned with is the application of a one-size-fits-all mentality to the provision of information technology to a company’s workforce, as well as the imposition of blanket security regulations that serve to cripple an organization’s ability to keep abreast of developments in that same technology. This becomes increasingly important as more capability moves out into the cloud (this includes micro-cloud environments, i.e. inside the firewall capability that utilizes cloud-like architecture.)

I have tried to argue, to no avail – I’m sure others will recognize this particular kind of frustration – for the identification of power users who could be provided with, for lack of a better term, beta capabilities they would exercise and learn about. These people would provide a cadre of workers who are constantly looking at new ways to improve communication, collaboration, and findability. People who’s job, in part, is to find newer and better ways to get things done. In my eyes, this is a no-brainer, and I have to say with the speed things are changing nowadays, I think this kind of approach is even more important.

I recognize it is difficult to get large organizations to move rapidly. One doesn’t turn a battleship on a dime. Nevertheless, it is conceivable to me (much more so now than a decade ago) a small group of people could help any organization understand – at the very least – how work gets done, how workers are communicating and collaborating with each other across various boundaries, and how knowledge is being shared in a timely and useful fashion. I also think, daring as it may seem to some, that paying attention to – and preparing to learn from – the processes that are changing the way we do these things can position a company competitively to be a player, rather than an also-ran. I quite certain failing to do so leaves you with the situation I grew used to; a company with computing resources and experience years behind state-of-the-art. In marketplaces where this can change dramatically in under a year, I think that’s unconscionable.

Have any of you experienced this situation? Does it resonate at all? Am I totally off-base or do you think this would be a viable approach for large organizations to engage in?


Inclusion: Bad for Diamonds; Oxygen for Innovation

In a response to a tweet from @MartijnLinssen, I noted that inclusions are bad for diamonds, but good for innovation and business in general. I think Martijn posted that particular tweet in response to a question I had posted about the use of the terms “consultant” and “expert”. I think too much time is spent on figuring out ways to exclude people from anything other than the roles we’ve pigeon-holed them in. This seems to be the default mode of Human Resource departments, i.e. find a job title and wrap it around a “belly button”. Once you’ve accomplished that task, you have an employee ready to fit into the pre-ordained mold you’ve created; the cog in your machine, if you will.

This seems to miss the reality that all of us are far more complex than a title can contain expression for. In my over twenty years at Pratt & Whitney Rocketdyne I have seldom performed tasks that were directly in alignment with the title I held. Part of the reason for this is I was always looking for new and innovative ways of getting things done and, to their credit, my management never (or seldom) discouraged me from doing so. I don’t think I’m all that unique. I happen to believe everybody has hidden skills and talents an organization can – and should – tap in to. We should encourage, no, assist everyone to reach their fullest potential. We should create an environment where everyone can contribute to the growth and sustainability of their organization, whether their contribution is small or large. To do anything else is more than foolish. It’s wasteful and destructive. Our people are, indeed, our most valuable asset – especially in a knowledge-based economy. An asset we can ill afford to ignore.


Are We Failing to Fail?

Today I attended an hour and a half, lively, funny presentation by a man I had never heard of before, but who I intend on paying at least a little more attention to in the future. His name is Terry Paulson. He’s been described as the Will Rogers of Management Consultants and he pretty much lives up to that description. He was invited as part of a series of ongoing events put on at Pratt & Whitney Rocketdyne called Passport to Leadership. This series is always open to anyone who wants to attend. Due to space limitations there is online registration available on a first-come, first-serve basis. Most of the time, unfortunately, the room (generally it’s held in an auditorium that can seat about 150 people) isn’t quite full. Sometimes it’s overflowing; depends on the speaker, the time of year, and what’s going on in the company at the time.

I chose to attend this particular event not because I had any idea who Terry Paulson was, but because of the title of the event – “The Innovative Leader’s Challenge: Inventing the Future in a Cost-Containment World”. Intriguing. Surely, anyone paying attention nowadays knows just about everyone is paying attention to costs more so than usual. What I really liked about his approach was its level of (in the words of his website) optimism, resilience, and hope – not to mention a good dose of animated humor. He made it clear he wasn’t talking about being a Pollyanna,  full of false promise and glittering visions of the future, but of being a realist; of looking at things and seeing them for what they are and being willing to face them head on. Interestingly, though he didn’t say it, his home page talks about something I heard many years ago from a radio psychologist by the name of Dr. Toni Grant. I used to listen to her on KABC radio here in Los Angeles when I was driving a truck in my family’s wholesale food business back in the late 70’s. She talked about the propensity many people have to be perfectionists, and she said perfectionism was the beginning of what she called “The Three Ps” – Perfectionism, Procrastination, Paralysis. Many people who read this recognize how frequently this is the case. I know I’ve experienced it at times in my life.

Here’s a quote from his website that kind of sums up the presentation he gave: “Most get an ‘F’ where it counts the most. They fail to fail! Too many get stuck in the Three P’s: Perfection, Procrastination, and Paralysis. They are so worried about making a mistake that they end up doing nothing at all. Most mistakes are not terminal; they become stepping stones to success. Get moving!”

At any rate, here are some of the takeaways I have from this presentation:

  • Frequently ask people questions like “What are you doing differently” or “What have you learned lately?” or “What’s working for you?”
  • When you attend a conference or a presentation don’t sit with people you know (they’re “used”)
  • Don’t wait for direction; get busy inventing the future by capitalizing on emerging opportunities
  • Continually use your quality processes and innovation as a strategic advantage to create the new “good old days”

Here are a few other concepts he discussed . . . and passed out in a nice handout I can easily copy them from 🙂

  • Claim the optimism advantage by using setbacks as stepping stones to progress
  • Build a learning organization in support of strategic innovation
  • Use bridge building strategies to make collaborative innovation work

One of the things I found most amazing about his presentation was every slide he showed was a quote by someone else. Normally I would find this abhorrent but, in his case, he supplemented every one of them with his own stories and anecdotes and his spin on what the message of the quote was. Even the way he read them was entertaining. He was very animated, very funny, very entertaining, and pretty damn enlightening. Like many presentations I’ve attended, he didn’t necessarily tell me anything I didn’t already know. Nevertheless, his style – and his substance – reinforced many of these things, either reminding anew of those things I perhaps needed to strengthen my skill at or providing some positive reinforcement that I’m heading in the right direction.

One of my favorite quotes (at least a portion of one) comes from Barbara Waugh, a personnel manager and change agent at Hewlett-Packard. She has talked about “amplifying the positive deviants”. I like to think she was talking about me when she used that term.


Are We Really Communicating All That Better?

In my over twenty years of experience at the large, very successful aerospace company where I labor, I have spent a great deal of time trying desperately to get the IT people to talk to the Engineering people. I haven’t, for the most part, been all that successful. Back in the day IT was truly an empire unto itself and it was pretty blind when it came to listening to the needs of the Engineering community. Furthermore, many of the systems that were used by various programs were dictated by the customers who were paying for our services and our products, basically NASA, the U.S. Air Force, and DOE.

This resulted in some very interesting problems with respect to systems, tools, and their use and subsequent development. What used to happen was Engineering would get an itch for a certain type of functionality but, since it hadn’t been contemplated in the original contract and since it might be some time before it could be renegotiated in order to get some money for developing the code required, Engineering would take it upon themselves to develop what they needed. You can imagine what happened many times. Though not an Engineer myself, I believe all Engineering students study one or more computer languages . .  . I’m fairly certain most of them  do.  Well, they would just get on the problem themselves, either writing code or – even worse – creating a tool in Excel.

So now we find ourselves in the interesting position of having something like a couple hundred tools, many quite useful, many overlapping in functionality. Many of them are unwieldy and kind of out-of-date, yet we don’t quite know how to get rid of them. This does seem to be changing somewhat as the tools of Enterprise 2.0 are gaining traction, i.e. blogs, wikis, user-generated content in general. Regardless, there are still numerous choices for how to deal with each of these as well. What wiki should we use? What about Open Source? (Anathema, btw, in my company – at least for now).

So the beat goes on. We keep adding tools, if at a slightly slower rate than previously (I think), and we seldom shed any. I suspect, as more and more content gets generated through the use of social media, and the ability to organize and make sense of it improves, we will eventually move away from many of the tools we’ve kind of grown up with. Data, too, will probably migrate toward a common format that can be accessed easily by anyone who wishes to and has authority to do so. It would be nice to see everyone on the same page, rather than pockets of people talking about the same thing in slightly different, and frequently incompatible, formats and locations.


%d bloggers like this: