Category Archives: Knowledge Management

Decision Intelligence Plus Knowledge Management Plus Foresight

Just started reading Link: How Decision Intelligence Connects Data, Actions, and Outcomes for a Better World. Great read and I encourage you to read more about the emerging field of decision intelligence.

Woman surrounded by flying books.

As I am reading the book, I’m taking notes that will eventually turn into a model of combining knowledge management and foresight with decision intelligence. There are some powerful parallels here. And decision intelligence seems fit for knowledge automation.

Eight Reasons Why Your Collaboration System Is Failing

At the beginning of this year, I swore off using Slack. My resolution amazed my friends who extolled the virtues of Slack. Slack isn’t the collaboration app proclaimed to be the “next big thing’” I remember back in the early 90′s when computer-supported work applications were all the rage (remember when “Lotus Notes” was first rolled out). Organizations threw a lot of money and resources at early collaboration systems, but many were failures from the beginning.

The failure of many new collaboration systems to catch on was perplexing because software packages for individuals and organizations were doing well. What was it about developing software for groups that made it so different from developing software for individuals and organizations?

In 1994, Dr. Grudin published an article that answered that question with the simple observation that groups were just different from individuals and organizations. How they are different is explained in his eight challenges for developers:

People collaborating in front of a laptop.

Who Does the Work and Who Gets the Benefits? Ideally the labor in operating and maintaining the groupware application must be roughly equal among the group members. This ideal division of labor is rarely the case. Consider a project management application where the team members must update it regularly with progress reports, performance data, and other data. A good deal of the team member’s team is compiling information and feeding the system while the project manager must spend a minimal amount of time reading reports the system generates. The team member sees only a burden from the software and soon avoids doing this extra work which leads to poor reports causing the Project Manager to quit relying on the system for information. Soon, no one is using software.

Critical Mass of Users. The collaboration software field is filled with many platforms for collaboration. Many offer similar features, and each has an enthusiastic community of supporters. In large government agencies you can see several collaboration systems in various pockets of the organization that don’t communicate outside of their pocket. Ironically the systems that exist to promote collaboration often promote organizational silos as the groups argue that their system is the best solution.

Social, Political, and Motivational Factors. Dr. Grudin gives a great example of this challenge when he describes the failure of meeting management software. It assigned meeting rooms based on priority but quickly became useless because no one wanted to admit that their meeting was anything but “high priority.” As Dr. Grudin explains, collaboration software can only model a rational workplace, but actual workplaces are much more complicated due to organizational culture.

Exception Handling. We rarely work the exact way described in our work processes. Collaboration software built only based on the documented office procedures is too rigid and not able to handle the flexibility required frequently at work. Just think of how often you don’t have a typical day at work and have to improvise a workable solution. Now, imagine trying to program that into software.

Decreasing Communication and Coordination Load. Organizations search for ways to reduce the communication and coordination needed to do the job. How often have you said that you could get more done if you were not interrupted so often? Of these interruptions, how many were due to email, phone calls, a colleague stopping by to talk, etc.? Sometimes you can over-collaborate, and this often results from poorly designed groupware.

Hard to Evaluate Groupware. It is challenging to test groupware because the group dynamics are so hard to replicate. It can take several weeks of careful observation to understood how a group works, and software designers don’t have the time or expertise to evaluate how their software will aid in collaboration. Often the groupware vendor blames this on inadequate user training and will continue the same software with better tutorials and help aids but never realizing that the fundamental problem is that people don’t like collaborating the way the system is forcing them to collaborate.

Intuitive Decision Making. Because of the nature of our work, we often must decide based on little evidence, and thus we rely heavily on our intuition. Groupware applications rarely support intuitive decision making but force users to input significant data so a fully reasoned decision can be made. Often, we do not have the necessary data, and a quick decision must be made. Thus, we abandon the groupware application to use a simple spreadsheet or other individual application to support our intuition.

Managing Acceptance of the Groupware. Too often, I have seen a collaboration solution launched where the users are expected to adapt themselves to how the software works rather than the software adapting to the way the group works. A collaboration system at my work is universally despised because it practically handcuffs a group of users to a cumbersome and protracted painful process. I’ve only used the system once, but that was enough for me to avoid ever having even to click on the program icon.

Despite these principles being 25 years old I still see the same mistakes being repeated in today’s collaboration tools. I also see where companies have put these principles into practice and have made excellent collaboration software that has endured and grown in popularity. I suspect that Google engineers must have memorized these principles when they developed their Google Docs system.

I leave a final exercise for the reader: how many of these principles does SharePoint violate (if any)? Or does SharePoint violate new principles of collaboration software?

“You’re so dumb!:” The Next Generation

“Our youth now love luxury. They have bad manners, contempt for authority; they show disrespect for their elders and love chatter in place of exercise; they no longer rise when elders enter the room; they contradict their parents, chatter before company; gobble up their food and tyrannize their teachers.”

The above complaint was from Socrates. St. Thomas Aquinas lamented that the world would be left to an ill-prepared and careless youth. A year after I was graduated from college, I read Steve Allen’s Dumbth which “humorously” recounted tales of how Generation X didn’t know how to think.

Thirty years later it’s the Millennial Generation’s turn with The Dumbest Generation label (and Generation Z not far behind). “According to recent reports from government agencies, foundations, survey firms, and scholarly institutions, most young people in the United States neither read literature (or fully know-how), work reliably (just ask employers), visit cultural institutions (of any sort), nor vote (most can’t even understand a simple ballot). They cannot explain basic scientific methods, recount foundations of American history, or name any of their local political representatives. What do they happen to excel at is – each other. They spend unbelievable amounts of time electronically passing stories, pictures, tunes, and texts back and forth, savoring the thrill of peer attention and dwelling in a world of puerile banter and coarse images.”

The crux of the “dumb generation” argument is that their generation doesn’t have the knowledge that our generation has with the implication that our knowledge is inherently superior. It reminds me of summers that I spent at my grandparent’s farm where I was pitied because I didn’t know how to milk a cow, can vegetables, or could identify all the trees on the farm. “Didn’t I know anything?” they asked.

Then, I bought my grandparents a microwave oven, a VCR, and hooked their TV up to cable. Now I got to mutter under my breath, “didn’t my grandparents know anything?” As our workplaces become multi-generational, I am sure there is a lot of grumbling about the limitations of the different generations. And that is wrong.

Young girl walking with an old man.

The real issue is how to transform our organizations into learning organizations, so we capture the knowledge we already have and determine the knowledge we need. We produce new data and information at an astounding rate, and it is growing faster every year. The challenge is to determine what knowledge we need to keep, what knowledge we need to discard, and how to find the new knowledge we need. Like the way I cling to 1980s rock, knowledge we already have feels comforting and empowering, but we need to have the courage to let some of that go and embrace the new knowledge being produced. We also need to recognize that not all old knowledge is useless and should be discarded.

Others have written that the best learning is in our workplaces and with conversations with our colleagues. We can learn a lot from each other, and our organizations desperately need our efforts to keep the organizational memory growing and thriving. That means younger workers should not just immediately dismiss current practices and processes because that is how they used to do things. And older workers should not be defensive and dismissive when younger workers suggest new ways of doing the organization’s business.

Back when I worked at a state agency, I had a colleague who insisted on using Lotus 123 for his spreadsheets, although we had Microsoft Excel. He would bitterly complain when they tried to install Excel on his machine, and we would have to support Lotus 123 even though it was getting harder to do so every year. I then hit upon a strategy of having him teach me his spreadsheets. I would go over to his cubicle and learn the macros he created. I would recreate the macros in Excel and then show him how much more powerful they were and how the reports looked better with charting available to Excel. He was reluctant at first, but what sold him on upgrading is that he would not lose the original knowledge he had in his spreadsheets and macros but that they would be faster and more effective in a newer environment. Two years later, he relished his role as the “Excel Guru” who was the go-to guy about the intricacies of Excel spreadsheets.

So, maybe what is needed are fewer books about how stupid the other generations are and more books on how much we can learn from each other.

U.S. Congress Finds One solution to It’s Information Problem

The U.S. Congress’ Select Committee on the Modernization of Congress has created the United States Legislative Markup (USLM) to standardize the format for drafting, viewing, and publishing legislation.

Open book with a page of text

Importantly, this standardization means that rule of law nations can help each other far more effectively. It means that –at long last– democratic values might be able to beat the trolls, out compete data mercenaries and diminish the information weaponization that is paralyzing democracy worldwide. This global democratic resilience will be especially important when we arrive at machine learning, artificial intelligence and algorithms. Will we build an auditable public good system? One that can visualize and help forecast implications of policy? One that is able to identify misinformation and financial conflicts of interest in the data supply chain? Or, will this new openness become yet another opportunity to commodify, privatize and capture democratic functions?

The USLM is a great step toward tackling the increasing data overload of Congress and the federal government as a whole.