Writing of a different style, fiction, or at least I hope so…Overcommitted

It is 8 AM and Sam Houston is on his way to his office in downtown Chicago. He drives from his house in Libertyville, a northern suburb of Chicago, then catches a train into the city. During his roughly seventy-five minute train ride, he has learned to balance his laptop, notebook and pencil, his blackberry, and his triple shot frappuccino coffee. He begins his trip by reviewing his agenda for the day, thinking through his upcoming meetings, his to-do list, and the projects under his supervision.

For some reason, today Sam finally comes to the realization that he is overcommitted.  He thinks to himself, "I need to cut things off my lists!" (Good for you, Sam!) As Sam tries to think of solutions, he cannot resist the temptation of going through the mail that came in during the night. Alas, he sees that both Susan and Charlie have asked him for ‘small’ favors that would require him to be part of two different teams- one exploring strategic priorities for the organization, the other making a decision on which vendor the organization should choose for its new social media platform re-design. Sam knows that he cannot turn these opportunities down; they are both critical to his career, not to mention that he does owe both Susan and Charlie favors for their help on one of his past efforts. Sam tries to think how he might organize his tasks and prioritize his ‘big ticket’ items. As he works on his list, he hears the soundtrack of ‘We are Champions’ by Queen playing, and he rushes to silence his ringtone by answering his blackberry. His wife is calling to remind him that he has three social events on his calendar in the next two days. Reluctantly, Sam acknowledges that he had promised to attend two school events for his children and visit his in-laws for a birthday celebration. Becoming frustrated at his increasing commitments, Sam has now forgotten what he was doing before the phone call and he is also reminded that he is only two stops from Union Station. He begins to pack his stuff up, takes a moment to enjoy his now cold caffeine drink, and takes a quick glance at the headlines from the Chicago Tribune. The train makes its entry into Union Station and Sam walks briskly to the exit where he hails a cab to take him to his offices in the Merchandise Mart. As he takes the elevator up and heads into his office, he makes a mental promise to himself, "No more commitments today. No matter what, I have to say no!" Sitting in his comfy leather chair and taking a moment to enjoy the view of Lake Michigan from his office window, he is interrupted by his assistant who tells him about an emergency meeting that is being called by the CEO. Sam realizes that today may not be the right day to say no…

Can you connect with the above scenario! Unfortunately, (and yes, I do mean unfortunately) may of us can. As much as we try, we never seem to manage our ever increasing commitments. We over-commit and continuously extend ourselves. Many of us  can do this for seemingly good reasons. We want to seem helpful or we do not want to allow opportunities to slip us by.  Other times, we may have underestimated the resource and time investment that the various commitments would require of us. Commitments do come due, and troubles build as the timelines draw near. We get irritable and annoyed with ourselves and the tasks at hand. As a result, the quality of our work suffers, both in terms of the output that we deliver and the process that we employ to arrive at the output. In the final analysis, we, as individuals, suffer. Our quality of life is impacted.

If you have strategies, decision-tools, or process frameworks that you use to manage your commitments, both in terms of identifying how to decide what commitments to take on and how you manage your ongoing commitments, please share them with me... and with Sam!

P.S. My wonderful students of IMT 580 the last year brought me a fiction book. I enjoyed reading it. So, here is my first attempt at writing what I hope is fiction (based on reality, of course!)…Stay tuned for the entire book, if I ever manage to stay focused on my current commitments!

A Longitudinal Analysis of Stakeholder Sentiments: Business Modernization Project at the IRS

The Internal Revenue Service Business Modernization Project undertaken by the Tax Agency of the US Government has been singled out as an example of a massive failure. As envisioned, the project was intended as an Enterprise-wide intervention that would provide modern services and effective data access to citizenry and several government agencies. After more than a decade and 3 billion dollars later, the results appear to be less than exemplary. Sandeep Purao and I have a paper accepted for presentation at the Enterprise Architecture Research (TEAR2010) Workshop that identifies different stakeholders who participated in the project, and analyzes the sentiments and confidence each expressed regarding the fate of the project. We conclude with lessons learned from our investigation including recognizing the importance of multiple stakeholders for Enterprise-wide initiatives.

Purao, S., and Desouza, K.C. “An Enterprise-wide Intervention at IRS: A Longitudinal Analysis of Stakeholder Sentiments,” In Proceedings of the 5th Trends in Enterprise Architecture Research (TEAR2010) Workshop,  Delft, Netherlands (November 12, 2010).

Speaking at Bangkok University on Designing the Innovation Process

I will be giving a talk at Bangkok University (Kluaynamthai Campus) on designing organizational innovation processes. The talk is organized by Institute for Knowledge and Innovation South-East Asia (IKI-SEA) as part of their KM World Seminar Series and will take place on October 28, 2010 from 1.30 PM to 4:00 PM. Please click here to download the flyer.

Interview with KM Leaders: Stan Garfield

I am currently interviewing an eclectic group of knowledge management leaders on their experiences. These interviews will appear in my new book on knowledge management. Here is an excerpt from my interview with Stan Garfield. I first met Stan Garfield at the APQC Conference in St. Louis in 2005. I was immediately impressed with his depth of knowledge and experience. He invited me to give a talk to his knowledge management community of practice soon after. Through the years, I have kept abreast of his work in the knowledge management field. Through this interview, I am hoping that you will gain an appreciation of what it takes to be a KM leader.

Current Title and Organization: Community Evangelist, Global Consulting Knowledge Management, Deloitte Touche Tohmatsu Limited

Biography: Mr. Garfield began as a computer programmer, research assistant, and manager at Washington University School of Medicine and St. Louis University from 1975-1983. He then moved to Digital Equipment Corporation (later, Compaq and HP) and held a wide variety of field and headquarters management roles in presales, consulting and system integration. Among his many achievements, he launched DEC’s first knowledge management program in 1996, helped develop the corporate KM strategy for Compaq in 2000, and led the Worldwide Consulting & Integration Knowledge Management Program for Hewlett-Packard, 2004-2008. After leaving HP, he briefly served as Retail & Consumer Knowledge Domain Manager at PricewaterhouseCoopers, before joining Deloitte Touche Tohmatsu Limited as Community Evangelist in Global Consulting Knowledge Management. He lives in Northville, Michigan.

How do you define knowledge management?

Knowledge Management (KM) is the art of transforming information and intellectual assets into enduring value for an organization’s clients and its people.  The purpose of knowledge management is to foster the reuse of intellectual capital, enable better decision making, and create the conditions for innovation. KM provides people, processes, and technology to help knowledge flow to the right people at the right time so they can act more efficiently and effectively.  To practice knowledge management, share what you have learned, created, and proved; innovate to be more creative, inventive, and imaginative; reuse what others have already learned, created, and proved; collaborate with others to take advantage of what they know; and learn by doing, from others, and from existing information.

Can you tell us a bit about your first job as a knowledge manager and how did you get this role (i.e., how did you make the transition to a knowledge manager, if it was not your first job)?

In 1996 I was asked by the senior vice president of systems integration at Digital Equipment Corporation to start a knowledge management program after we visited Ernst & Young's Center for Business Knowledge in Cleveland, Ohio.  When he heard that Ernst & Young had a Chief Knowledge Officer, he turned to me and said, "I want you to be our CKO."  I had been doing knowledge management for many years in addition to my official duties in professional services management, but we didn't call it that.  It has been referred to as something like "resource management" or "capability development" or "information."

My job was to launch the first KM program at DEC.  I had to define the strategy and approach we would use, and start the process of implementing changes incorporating people, process, and technology elements. Along the way, I had to endure many ups and downs, enlist allies in the cause to join my virtual team, get executive sponsorship from a succession of leaders, increase investment and commitment to the program, deal with constant organizational change, adjust to changing technology, migrate from and integrate with legacy software, exercise diplomacy with many other groups, and cope with two large-scale corporate mergers.

Thanks. What did you learn from this experience? What were three of the major challenges you faced? How did you overcome these challenges?

I learned:

  1. Put a strong KM leader in place, and ensure that the KM team has only strong members.
  2. Balance people, process, and technology components, with a project leader for each category.
  3. Establish a governance and collaboration process to engage all groups within the organization (e.g., business units, regions, functions), and to formally manage and communicate on all projects – appoint KM leaders in each major group.
  4. Hold annual worldwide face-to-face meetings to get all KM leaders informed, energized, and collaborating.
  5. Communicate regularly through newsletters, training, web sites, and local events.
  6. Get the senior executive to actively support the program.
  7. Engage with other KM programs, both internal and external, to learn, share ideas, and practice what you preach.
  8. Focus on delivering tangible business benefits that match the overall objectives of the organization.
  9. Deliver regular improvements to make the KM environment effective and easy to use.
  10. Set three basic goals for employees and stick to them for at least a year.

Three keys to the success of a KM program:

  1. Set three simple goals and stick with them for the long term.  Communicate them regularly.  Incorporate the goals and metrics into as many parts of the organization as possible (e.g., employee goals, incentive and rewards programs, and newsletters).
  2. Keep the people, process, and technology components of the KM program in balance.  Don't allow one element (e.g., technology) to dominate the other two.
  3. Lead by example.  Model the collaboration and knowledge sharing behaviors you want the organization to adopt in how you run the KM program.

Five pitfalls to avoid:

  1. Trying to take on too much.
  2. Focusing on technology.
  3. Not engaging the constituents.
  4. Doing too much studying and planning and not enough prototyping and piloting.
  5. Not reusing what others have already learned and implemented.

Can you say a bit more about the pitfalls, especially how did you manage not to take on too much. I have heard from a lot of KM leaders that the number one reason they fail is that they over promise and under deliver. What strategies do you recommend for budding managers?

Pick one focus area which addresses a widely-perceived need, where you can achieve positive results relatively quickly, and which can be implemented without the need for extensive approvals, expenditures, or custom development.  Direct most of your energy and resources behind this effort, and when it succeeds, pick the next focus area using the same criteria.

Find out if the senior executive has a hot button, pet project, or wish list.  Respond to these by implementing something for them, getting their endorsement and participation, and then widely communicating how everyone else in the organization can emulate the leader.

Pick the three goals and repeat them in all communications until everyone knows them.  Relentlessly stick to achieving these goals until you can declare success on one or more of them.  Then pick new ones and repeat the process.

Harness the efforts of others and connect their people, processes, and tools into your program.  For example, if another group has implemented a blog platform that your program can use, embrace that as your blog platform rather than launching your own.  If yet another group has an innovation process, adopt it as yours.  And invite people outside your group to participate in your activities as virtual or extended team members.

Thanks. Can you please also say a bit about the importance of prototyping and piloting approaches and solutions to KM?

Classic software development projects included lengthy time allocations for analysis, design, and development before users ever had a chance to try out the results.  Given that it is difficult to know exactly what features users want and how they should actually work before using a new program, the "finished product" would often be unsatisfactory to the users for which it was developed, despite the fact that it met their specifications.

Knowledge management programs and intranet systems often make the same mistakes as software development projects.  Lengthy designs or redesigns are followed by big launches and then by users disliking or ignoring the touted offerings.  I call this the "big bang" approach, such as when a new or revised web site is unveiled after six months of development, only to miss the mark as judged by its intended audience.  What are the users supposed to do during the time prior to launch?  It's much better to quickly launch a simple site serving up the most important content (as defined by the users) and then continue to improve the site and add more content on an ongoing basis.  This results in a site which is both immediately useful and which is also perceived as being continuously improved.

Whenever you have a potentially good idea for a people, process, or technology innovation, try it out as soon as possible.  Start by discussing it with a group of trusted colleagues, fellow members of a community of practice, or insightful friends and family.  Mock up a simple picture, screen shot, or process flow.  Encourage candid comments and suggestions, and incorporate as much of this feedback as possible in your initial design.

Implement your idea directly, through a colleague, or through a team good at development.  Do this sooner, rather than later.  Publicize your initial implementation through a relevant community of practice, your social network, and your work team.  Solicit feedback for improving functionality, usability, and effectiveness.  Then quickly make improvements and repeat the cycle.  Continue this process indefinitely, with longer cycle times as functionality better aligns with user requirements.

Over the years, can you describe what has changed in your approach to leading knowledge management programs in organizations?

My approach has evolved as opposed to changed.  I emphasize understanding the needs of the organization and responding to those needs, rather than trying to roll out a system and try to get it adopted.

Here are 13 insights I have drawn from my 14 years in KM:

  1. Collect content; connect people
  2. Try things out; improve and iterate
  3. Lead by example; model behaviors
  4. Set goals; recognize and reward
  5. Tell your stories; get others to tell theirs
  6. Use the right tool for the job; build good examples
  7. Enable innovation; support integration
  8. Include openly; span boundaries
  9. Prime the pump; ask and answer questions
  10. Network; pay it forward
  11. Let go of control; encourage and monitor
  12. Just say yes; be responsive
  13. Meet less; deliver more

To read more about the interview, stay tuned for the book…

To be interviewed or recommend renowned KM leaders and managers for interviews, please send me an email.

Looking for Clues to Failures in Large-Scale Public Sector Projects

Sandeep Purao and I have a paper accepted at the 44th Hawaii International Conference on System Sciences in the Electronic Government Track (Development Methods for Electronic Government, Minitrack). The paper analyzes the IRS’s Business Systems Modernization Project using sentiment analysis.

We describe results from historical analysis of a large-scale, public sector effort: the IRS Modernization Project that has already spanned a decade and consumed more than 3 billion dollars. The results focus on analysis of Sentiments and Confidence expressed by different stakeholders, as found in various documents. We explore how such analyses may provide a window on project progress and potential early clues that may contribute to preventing undesirable outcomes in the future.

Reference: Purao, S., and Desouza, K.C. “Looking for Clues to Failures in Large-Scale Public Sector Projects: A Case Study,” In Proceedings of the Forty-Forth Hawaii International Conference on System Sciences (HICSS-44), Los Alamos, CA: IEEE Press, Kauai, HI, (January 4-7, 2011).

Large IT Projects as Interventions in Digital Ecosystems

Sandeep Purao (IST, Penn State University) and I have a paper accepted for presentation at the International ACM Conference on Management of Emergent Digital EcoSystems (MEDES’10) (BangkokThailand).

Abstract: Large IT projects, such as the US Government’s Internal Revenue Service Business Modernization Effort, can take a decade or more and consume billions of dollars. Traditional approaches to the study of such projects emphasize concerns such as requirements monitoring, progress tracking and risk mitigation. We propose an alternative approach guided by a digital ecosystems view instead of a hierarchical, decision-oriented view. We argue that this perspective is more suited to understand how such projects evolve and cause changes in the underlying digital ecosystem characterized by not only the IT infrastructure but also the transactional relationships among stakeholders. We illustrate our arguments by drawing on an archaeological case study of the IRS effort, and discuss implications of the digital ecosystem perspective for the study of large IT projects.

Reference: Purao, S., and Desouza, K.C. “Large IT Projects as Interventions in Digital Ecosystems,” In Proceedings of the International ACM Conference on Management of Emergent Digital EcoSystems (MEDES'10), Bangkok, Thailand (October 26-29. 2010).

Consulting and Advisory Services

I have updated the Consulting page on my website. Consulting engagements I offer range in scope from single-day senior executive briefings to small-term strategic project assignments. Here are some of the most common offerings:

Executive Strategic Planning Retreats: Working closely with the client, Kevin scopes out a keynote presentation followed by a workshop. The day begins with the keynote and a thought provoking discussion. The workshop can be used to facilitate corporate strategic planning and design, forecasting and planning for future trends that impact the business, or brainstorming and consensus building. Past retreats have focused on strategic innovation, designing collaborative alliances for organizational resiliency, and building crisis detection and response programs.

Strategic Advising and Consulting: These short-term engagements allow Kevin to work intimately with the client on focused areas of strategic opportunities and challenges. Advising and consulting projects range from strategizing knowledge management and innovation endeavors to technology management projects and competitive intelligence assignments. Past engagements have included advising a major engineering firm on designing a knowledge management program, reviewing business plans and specifications for products of a major technology organization, and serving as a senior adviser for market and customer intelligence projects.

Ideation and Commercialization: This unique offering by Kevin is centered on helping entities leverage their ideas. Kevin works with entities ranging from individual executives in leading organizations, to technology start-up firms, to independent thinkers (e.g., scientists, bloggers, and product designers). The focus is to help entities manage their ideas optimally for goal attainment. Past engagements include working with senior executives to publish their ideas in mainstream journals or books and helping technology start-ups formulate key strategic alliances.

Keynote Address at the 2010 Computational Social Science Society Conference: From Hunches to Evidence Driven Policy Design

I will be giving a keynote address at the 2010 Computational Social Science Society Conference (CSSS). CSSS 2010 is hosted by the Center for Social Dynamics and Complexity and the Consortium for Biosocial Complex Systems at. For more information on the conference, please click here [LINK].

From Hunches to Evidence Driven Policy Design: Leveraging Information through Simulation

Constructing public policy, whether at the national or local level, is a complex undertaking. Complexity arises from the number of stakeholders involved, varying agendas and incentives, resource constraints, a multitude of interacting variables, multiple time horizons, and even political climates. Due to these complexities, we too often categorize political and social problems as ‘wicked’ and unanalyzable. The default option is to take a haphazard approach to policy design, most often the outcome of the ego-based debates and negotiations of the decision-makers. In this keynote address, I will argue for a move from hunches (or intuition) to evidence driven policy construction. Today, due to the advancement of computational power and modeling techniques, we can simulate complex scenarios. Simulation gives us an ability to move policy construction from an activity primarily driven by historic case analysis and intuitions, to more of an applied science, where we can actually predict and control phenomenon. Through simulation we can, with reasonable certainty, ascertain the cost, benefit, risk, impact, and value proposition of a given policy. Using examples from simulation projects, such as a project that examined strategic options for dismantling terrorist networks, I will demonstrate how we can move policy design from being an ‘art’ to more of a ‘science.’

Building Sustainable Collaborative and Open Innovation Programs – University of Ljubljana

I will be giving an invited lecture at the Raziskovalni center Ekonomske fakultete (Faculty of Economics) of the University of Ljubljana on February 15, 2010. My talk will focus on how organizations can design collaborative innovation programs.

Organizations cannot innovate in isolation. Ideas, knowledge, expertise, and processes needed for innovation are often distributed in the marketplace across a wide-assortment of actors from business partners, to customers, government agencies, and even competitors. Organizations have to find ways to collaborate and develop open, rather than closed, innovation programs. Collaboration calls for the ability to share required artifacts from ideas to knowledge and expertise, and even processes, with external entities. Being open requires an organization to unlock, and make available, its innovation process to external entities. Developing Collaborative and Open Innovation (COI) programs can be a daunting challenge. Issues such as ensuring trust, governance structures, rewards and incentives, and mechanisms for rent sharing from innovations can seem insurmountable. In this presentation, I will share actionable knowledge on how we can build sustainable COI programs. I will draw on research and consulting on designing organizational innovation programs in over 50 global organizations. I will share a framework for organizations that want to collaborate on innovation. This framework will outline methods for collaborative idea generation and mobilization, idea advocacy and screening, idea experimentation, idea commercialization, and idea diffusion and implementation. Examples will be used to illustrate how leading organizations collaborate with external entities for innovation and build open innovation programs that external entities can plug-into.

Speaking at the Washington Technology Industry Association: Securing Organizational Knowledge – Human Intelligence Operations

wtialogo_intI will be giving a talk for the Washington Technology Industry Association based on my recent book, Managing Knowledge Security (Kogan Page, 2007). The talk will take place on December 7, 2009 at Seattle University. For details, please click here [Link]

Based on his recent book, Managing Knowledge Security: Strategies for Protecting Your Company's Intellectual Assets (Kogan Page, 2007), Desouza will describe how human intelligence operations are conducted to ascertain competitive intelligence. Warning his audience of business practitioners that most organizations fail to understand that their core resources intellectual assets are constantly under attack, and that protecting these resources is as important as any other part of the strategic agenda. Desouza, gives advice on how to recognize dangers of human and technological breaches, hazards of outsourcing and business alliances, implementation of breach prevention measures, and the necessity of working with disaster scenarios. He illustrates his advice with cases from his personal experience working in the fields of competitive intelligence, knowledge management, crisis management, and security operations.