To download the paper, please visit - [LINK]
To download the paper, please visit - [LINK]
To download the paper, please visit - [LINK]
I will be delivering a plenary talk at the Cyber Storm International Conference on Weaponizing Information Systems for Political Disruption.
Click here to see the meeting agenda.
My recent post on US federal agencies cybersecurity preparedness on the Brookings Institution's TechTank blog has gotten a lot of attention. Jason Miller hosted me on his show, Ask the CIO, on Federal News Radio. Here is a link to the story and the interview.
I am thrilled to be invited back to address the Advanced Practices Council (APC) of the Society for Information Management. The APC commissioned a research report on mobile app development in highly regulated industries. Over the last few months, I have collaborated with Paul Simon (CEO of iHear Network and my former graduate student at the University of Washington) on this research report.The presentation will take place on Jan 22, 2014 at the Intercontinental Buckhead in Atlanta, Georgia.
Mobile App Development in Highly Regulated Industries: Risks, Rewards, and Recipes
Mobile computing has the potential to be as disruptive to the status quo as the introduction of the modern Internet in the 1990s or the Model T was nearly 100 years ago. Organizations need to not only understand the risks of mobile computing, but develop strategies to incorporate it before it fatally disrupts their current business model. Some of the rewards of a well thought out mobile strategy include increasing revenues or new revenue streams, greater brand awareness and customer loyalty, and a new set of tools to increase employee productivity. Firms in highly regulated industries face an even more complex set of challenges when considering how to approach the mobile space. Highly regulated industries have additional constraints for developing mobile software because of the additional layer(s) of regulation that dictate the protection and communication of information. It is important for these businesses to implement comprehensive security solutions that go beyond standard industry regulatory systems. Since regulations always lag behind technological advancement, organizations should think more proactively about how their actions might trigger future legislative responses and how their actions impact the user’s expectations of privacy and trust. Although there are risks associated with an organization’s increased use of mobile devices, the rewards that could flow from developing, implementing, and continuously iterating upon a coherent mobile strategy are enormous. In a Pew Research Center study, 63% of adult cell phone owners use their cell phone to go online, 34% said they do most of their internet browsing on their mobile phone. It would be detrimental to the long-term viability of an organization to ignore such trends. Traditional linear modes of developing strategy will not be sufficient or flexible enough to keep up with the rate of innovation in mobile hardware, software, and mobile operating systems. Design thinking has grown beyond just a methodology for developing software products and experiences and now a growing amount of managers are using design thinking as a means of developing business strategy. This non-linear mode of strategy development is better suited for building a mobile strategy as it will provide greater insight into the needs and desires of end users, foster innovative and creative solutions, and provide greater flexibility to adapt to the changing circumstances caused by the disruptive forces of the mobile revolution. This enables the Chief Information Officer (CIO) to provide greater leadership that leads to both internal and external innovative opportunities for mobile strategy development.
It has been a while since I wrote a paper on knowledge management systems, so it was a pleasant surprise hearing that the Journal of the American Society for Information Science and Technology has chosen two of my papers for their virtual issue on knowledge management. The two papers are:
I will be leading a workshop on knowledge management, focusing on designing sustainable knowledge management programs for talent management on June 7, 2011. My talk is sponsored by PLS Consulting as part of their Talent Management Strategies Series for HR Executives. The workshop will enable HR practitioners to:
Akshay Bhagwatwar (Indiana University), Ray Hackney (Brunel University) and I have authored a paper that appears in the current issue of Information Systems Management. The paper examines the knowledge re-integration challenges that organizations face as they try to take back previously outsourced IT operations.
Backsourcing is motivated by opportunities arising from changes in the business situation, redefinition of the character of outsourced service declining in quality or due to the discovery of flaws in the contract. The situation of backsourcing clearly has major implications for an organization in terms of monetary investments, IS infrastructure and changes in employee requirements during and after the process. The paper considers a detailed analysis of two case studies of backsourcing reported from JP Morgan Chase (USA) and Sainsbury (UK). A major contribution of the paper is to identify important strategies to be followed in backsourcing projects to ensure efficient knowledge re-integration.
Bhagwatwar, A., Hackney, R. & Desouza, K. C. (2011). Considerations for Information Systems “Backsourcing”: A Framework for Knowledge Re-integration. Information Systems Management, 28(2), 165-173
To access the paper, please click here: LINK
At long last, I have received information that my paper on Securing Intellectual Assets: Integrating the Knowledge and Innovation Dimensions will appear in International Journal of Technology Management (Vol. 54, No. 2/3, 2011).
Abstract: The concept of intellectual asset security has received widespread attention in recent times. Much of this attention can be attributed to the fact that knowledge assets can be used to secure competitive advantages for organisations. Moreover, one might assert that in today’s knowledge-based economies and markets, it is these assets that truly differentiate organisations and are the only true source of sustainable competitive advantages. In order to have a robust program for managing intellectual assets, an organisation must account for its knowledge management and innovation processes. In this paper, drawing on 1) a semiotic-based model for knowledge management (Desouza, 2006), and 2) an organisational process of innovation (Desouza et al., 2006), the author describes an integrated process framework for the management of intellectual assets. The framework is then used to describe salient security management challenges faced when managing intellectual assets. Executives involved in security management programs in 23 organisations were interviewed to elicit key security management challenges faced by organisations when addressing intellectual assets. The concept of intellectual asset security has received widespread attention in recent times. Much of this attention can be attributed to the fact that knowledge assets can be used to secure competitive advantages for organisations. Moreover, one might assert that in today’s knowledge-based economies and markets, it is these assets that truly differentiate organisations and are the only true source of sustainable competitive advantages. In order to have a robust program for managing intellectual assets, an organisation mustaccount for its knowledge management and innovation processes. In this paper,drawing on1 a semiotic-based model for knowledge management (Desouza, 2006)2 an organisational process of innovation (Desouza et al., 2006), the author describes an integrated process framework for the management ofintellectual assets. The framework is then used to describe salient security management challenges faced when managing intellectual assets. Executivesinvolved in security management programs in 23 organisations were interviewed to elicit key security management challenges faced byorganisations when addressing intellectual assets.
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.
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?
Three keys to the success of a KM program:
Five pitfalls to avoid:
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:
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.