Sections

Design Thinking: 8 Lessons Learned

Andreas Schmitz

A way to bring harmony to discordant teams? A technique for fostering empathy? Or a refuge from “command-and-control” leadership? Researchers from the Hasso Plattner Institute have taken a closer at what design thinking means to the business sector.

It seems as if even the most conservative of companies now has, in some corner or other, one or more of those colorful rooms equipped with jazzy chairs, randomly scattered cubes, wall-mounted screens, flip charts, and a startling array of writing utensils that are supposed not to show any resemblance at all to normal workday surroundings. But having a room like this is only the first step in a change process that needs to pass through many different departments in an organization.

More and more businesses have begun redesigning their work processes and their methods and now regard design thinking as a strategic management resource or, in some cases, even as a comprehensive management concept. A recent study by the Hasso Plattner Institute (HPI) reveals how 235 organizations view design thinking. Here are eight key lessons learned.

More and more businesses now regard design thinking as a strategic management resource.

1. Change outweighs savings

Revenue growth and cost-cutting are popular management goals, but they are not at the forefront of the design thinking concept. While 18% of the study respondents mentioned tangible cost-savings from design thinking, many more reported improved cooperation between employees (71%), more efficient innovation processes (69%), and better user integration (48%). Often, specific and significant changes are the result of incremental improvements to many internal processes and can’t be attributed solely to design thinking.

2. There are many variations

“What we’re increasingly seeing are examples of teams that are cooperating across departments and disciplines and focusing more closely on users and their needs,” is how Holger Rhinow, co-author of the HPI study, describes the current trend in many sectors of industry. But this transformation is not always a smooth one. In practice it doesn’t always follow the clear pattern that the design thinking training courses prescribe.

“At some point, companies need to free themselves from the “d.school” teaching concepts and adapt the methodology to their own contexts,” is the advice given by Jan Schmiedgen, a design expert and the study’s main author. User-centricity, iterative prototyping, and a mindset that is open to new ideas are all components that can make up a company’s individual innovation concept.

3. Research and development in the vanguard

More than 72% of the companies covered by the study limit the use of design thinking to selected business areas or departments, while only one in four (27.2%) has been able to establish it throughout the organization. The method is particularly popular in departments that thrive on reflection and creativity, such as research and development (named by more than 60% of the study respondents), marketing (40%), and consulting for internal support functions (31%).

4. “Command and control” is the death of design thinking

Everyone in a team contributes their own particular skills — an engineer will handle prototyping, for instance, and a social scientist will take on user research. “It’s vital that the leadership function rotates within the team,” says design expert Schmiedgen, who urges that everyone should work together as equals. The manager’s job is merely to describe the challenges, to moderate, and to ensure the team’s autonomy in every possible way.

For design thinking to be successful, it is vital that managers refrain from giving their teams instructions and that they leave them to tackle the problem on their own. “Management control,” says Schmiedgen “spells death to the development of new ideas.”

According to Schmiedgen, what companies wanted was innovation; what they got was team hugging.

5. Design thinking misused as a cure for discordant teams

Because design thinking has a reputation for encouraging collaboration, managers are apt to see the methodology as a way of getting teams and departments that have become embroiled in political intrigues to cooperate.

HPI researcher Schmiedgen has a stark warning about setting unrealistic expectations here: “Getting teams to a point where they’re willing to cooperate at all is a time-consuming process in its own right. But design thinking is first and foremost about encouraging innovation, not about harmonizing discordant teams.”

So, if design thinking is indeed being used as a kind of therapy, then managers should be wary of setting their expectations for innovation too high. In some cases, “What many companies wanted was innovation; what they got was team hugging,” says Schmiedgen. “But that’s not the fault of design thinking per se,” he adds.

6. Managers and employees must want change

For design thinking to become established in an organization, its management should function as an “enabler” of change in the corporate culture. It must also select its design thinking teams carefully.

“The employees involved must show a willingness to change and to recognize the attendant benefits. As a manager, it’s vital to think very hard about whether you want to muster the energy to convince the skeptics,” says the study’s co-author, Rhinow, who has been supporting workshops and innovation projects for the HPI Academy in Potsdam for many years.

7. No empathy, no results

Design thinking provides scope for “team intelligence,” which has a particularly beneficial impact on the users of products and so on. “The aim is to avoid bombarding users with cartloads of features that they don’t need, but to focus on making their lives easier,” says Rhinow, adding, “To do that, you need empathy for the customer.”

8. Design thinking takes time

You can’t just impose design thinking on a company from one day to the next. “You have to let it develop and grow,” says Rhinow. The new corporate culture needs time to become established. “Once you start using design thinking, you realize that there are other factors to contend with too,” adds Schmiedgen.

Because, as the study also shows, design thinking can’t be introduced in isolation without adjusting existing organizational structures and processes and without applying other management methods too – such as “lean startup” and “agile.”

Want more insight on design thinking? See Competing On Design Thinking.

Image via Shutterstock

Comments

Andreas Schmitz

About Andreas Schmitz

Andreas Schmitz is a Freelance Journalist for SAP, covering a wide range of topics from big data to Internet of Things, HR, business innovation and mobile.

How To Design Your Company’s Digital Transformation

Sam Yen

The September issue of the Harvard Business Review features a cover story on design thinking’s coming of age. We have been applying design thinking within SAP for the past 10 years, and I’ve witnessed the growth of this human-centered approach to innovation first hand.

Design thinking is, as the HBR piece points out, “the best tool we have for … developing a responsive, flexible organizational culture.”

This means businesses are doing more to learn about their customers by interacting directly with them. We’re seeing this change in our work on d.forum — a community of design thinking champions and “disruptors” from across industries.

Meanwhile, technology is making it possible to know exponentially more about a customer. Businesses can now make increasingly accurate predictions about customers’ needs well into the future. The businesses best able to access and pull insights from this growing volume of data will win. That requires a fundamental change for our own industry; it necessitates a digital transformation.

So, how do we design this digital transformation?

It starts with the customer and an application of design thinking throughout an organization – blending business, technology and human values to generate innovation. Business is already incorporating design thinking, as the HBR cover story shows. We in technology need to do the same.

SCN SY.png

Design thinking plays an important role because it helps articulate what the end customer’s experience is going to be like. It helps focus all aspects of the business on understanding and articulating that future experience.

Once an organization is able to do that, the insights from that consumer experience need to be drawn down into the business, with the central question becoming: What does this future customer experience mean for us as an organization? What barriers do we need to remove? Do we need to organize ourselves differently? Does our process need to change – if it does, how? What kind of new technology do we need?

Then an organization must look carefully at roles within itself. What does this knowledge of the end customer’s future experience mean for an individual in human resources, for example, or finance? Those roles can then be viewed as end experiences unto themselves, with organizations applying design thinking to learn about the needs inherent to those roles. They can then change roles to better meet the end customer’s future needs. This end customer-centered approach is what drives change.

This also means design thinking is more important than ever for IT organizations.

We, in the IT industry, have been charged with being responsive to business, using technology to solve the problems business presents. Unfortunately, business sometimes views IT as the organization keeping the lights on. If we make the analogy of a store: business is responsible for the front office, focused on growing the business where consumers directly interact with products and marketing; while the perception is that IT focuses on the back office, keeping servers running and the distribution system humming. The key is to have business and IT align to meet the needs of the front office together.

Remember what I said about the growing availability of consumer data? The business best able to access and learn from that data will win. Those of us in IT organizations have the technology to make that win possible, but the way we are seen and our very nature needs to change if we want to remain relevant to business and participate in crafting the winning strategy.

We need to become more front office and less back office, proving to business that we are innovation partners in technology.

This means, in order to communicate with businesses today, we need to take a design thinking approach. We in IT need to show we have an understanding of the end consumer’s needs and experience, and we must align that knowledge and understanding with technological solutions. When this works — when the front office and back office come together in this way — it can lead to solutions that a company could otherwise never have realized.

There’s different qualities, of course, between front office and back office requirements. The back office is the foundation of a company and requires robustness, stability, and reliability. The front office, on the other hand, moves much more quickly. It is always changing with new product offerings and marketing campaigns. Technology must also show agility, flexibility, and speed. The business needs both functions to survive. This is a challenge for IT organizations, but it is not an impossible shift for us to make.

Here’s the breakdown of our challenge.

1. We need to better understand the real needs of the business.

This means learning more about the experience and needs of the end customer and then translating that information into technological solutions.

2. We need to be involved in more of the strategic discussions of the business.

Use the regular invitations to meetings with business as an opportunity to surface the deeper learning about the end consumer and the technology solutions that business may otherwise not know to ask for or how to implement.

The IT industry overall may not have a track record of operating in this way, but if we are not involved in the strategic direction of companies and shedding light on the future path, we risk not being considered innovation partners for the business.

We must collaborate with business, understand the strategic direction and highlight the technical challenges and opportunities. When we do, IT will become a hybrid organization – able to maintain the back office while capitalizing on the front office’s growing technical needs. We will highlight solutions that business could otherwise have missed, ushering in a digital transformation.

Digital transformation goes beyond just technology; it requires a mindset. See What It Really Means To Be A Digital Organization.

This story originally appeared on SAP Business Trends.

Top image via Shutterstock

Comments

Sam Yen

About Sam Yen

Sam Yen is the Chief Design Officer for SAP and the Managing Director of SAP Labs Silicon Valley. He is focused on driving a renewed commitment to design and user experience at SAP. Under his leadership, SAP further strengthens its mission of listening to customers´ needs leading to tangible results, including SAP Fiori, SAP Screen Personas and SAP´s UX design services.

How Productive Could You Be With 45 Minutes More Per Day?

Michael Rander

Chances are that you are already feeling your fair share of organizational complexity when navigating your current company, but have you ever considered just how much time is spent across all companies on managing complexity? According to a recent study by the Economist Intelligence Unit (EIU), the global impact of complexity is mind-blowing – and not in a good way.

The study revealed that 38% of respondents spent 16%-25% of their time just dealing with organizational complexity, and 17% spent a staggering 26%-50% of their time doing so. To put that into more concrete numbers, in the US alone, if executives could cut their time spent managing complexity in half, an estimated 8.6 million hours could be saved a week. That corresponds to 45 minutes per executive per day.

The potential productivity impact of every executive having 45 minutes more to work every single day is clearly significant, and considering that 55% say that their organization is either very or extremely complex, why are we then not making the reduction of complexity one or our top of mind issues?

The problem is that identifying the sources of complexity is complex in of itself. Key sources of complexity include organizational size, executive priorities, pace of innovation, decision-making processes, vastly increasing amounts of data to manage, organizational structures, and the pure culture of the company. As a consequence, answers are not universal by any means.

That being said, the negative productivity impact of complexity, regardless of the specific source, is felt similarly across a very large segment of the respondents, with 55% stating that complexity has taken a direct toll on profitability over the past three years.  This is such a serious problem that 8% of respondents actually slowed down their company growth in order to deal with complexity.

So, if complexity oftentimes impacts productivity and subsequently profitability, what are some of the more successful initiatives that companies are taking to combat these effects? Among the answers from the EIU survey, the following were highlighted among the most likely initiatives to reduce complexity and ultimately increase productivity:

  • Making it a company-wide goal to reduce complexity means that the executive level has to live and breathe simplification in order for the rest of the organization to get behind it. Changing behaviors across the organization requires strong leadership, commitment, and change management, and these initiatives ultimately lead to improved decision-making processes, which was reported by respondents as the top benefit of reducing complexity. From a leadership perspective this also requires setting appropriate metrics for measuring outcomes, and for metrics, productivity and efficiency were by far the most popular choices amongst respondents though strangely collaboration related metrics where not ranking high in spite of collaboration being a high level priority.
  • Promoting a culture of collaboration means enabling employees and management alike to collaborate not only within their teams but also across the organization, with partners, and with customers. Creating cross-functional roles to facilitate collaboration was cited by 56% as the most helpful strategy in achieving this goal.
  • More than half (54%) of respondents found the implementation of new technology and tools to be a successful step towards reducing complexity and improving productivity. Enabling collaboration, reducing information overload, building scenarios and prognoses, and enabling real-time decision-making are all key issues that technology can help to reduce complexity at all levels of the organization.

While these initiatives won’t help everyone, it is interesting to see that more than half of companies believe that if they could cut complexity in half they could be at least 11%-25% more productive. That nearly one in five respondents indicated that they could be 26%-50% more productive is a massive improvement.

The question then becomes whether we can make complexity and its impact on productivity not only more visible as a key issue for companies to address, but (even more importantly) also something that every company and every employee should be actively working to reduce. The potential productivity gains listed by respondents certainly provide food for thought, and few other corporate activities are likely to gain that level of ROI.

Just imagine having 45 minutes each and every day for actively pursuing new projects, getting innovative, collaborating, mentoring, learning, reducing stress, etc. What would you do? The vision is certainly compelling, and the question is are we as companies, leaders, and employees going to do something about it?

To read more about the EIU study, please see:

Feel free to follow me on Twitter: @michaelrander

Comments

Michael Rander

About Michael Rander

Michael Rander is the Global Research Director for Future Of Work at SAP. He is an experienced project manager, strategic and competitive market researcher, operations manager as well as an avid photographer, athlete, traveler and entrepreneur. Share your thoughts with Michael on Twitter @michaelrander.

3 Ways Robots Will Co-Evolve with Humans

Christopher Koch

Comments

Christopher Koch

About Christopher Koch

Christopher Koch is the Editorial Director of the SAP Center for Business Insight. He is an experienced publishing professional, researcher, editor, and writer in business, technology, and B2B marketing. Share your thoughts with Chris on Twitter @Ckochster.

Tags:

Donuts, Content Management and Information Governance

Ina Felsheim

I was on vacation for two weeks, which was awesome, and my girls mainly wanted to do two things:

I had my own list of projects, too. The big one was installing glass tile on the kitchen backsplash. (Grout everywhere. That’s all I’m saying.)

After two weeks of glorious holiday, I sat down to take stock. The old technical writer in me came creeping out, and I began to count how many sets of instructions we followed over the course of the two weeks—more than 15, definitely. And the amazing thing? They were all right. Every. Last. One. From proper application of fabric paint to proper frying temperature for homemade donuts, to putting together a shoe rack that came in 20 pieces.

I’m pretty sure this wouldn’t have happened five years ago. The difference comes from an increased awareness in the importance of great user assistance. Without successful “use,” who’s going to evangelize your product?

Information Governance: Part of a Larger Food Pyramid

In EIM, we have a well-seasoned group of information developers. They apply information governance principles every day:

  • Create a single source of master information (in this case, product step-by-step instructions)
  • Manage versioning of master information (as product updates happen)
  • Survey end-users of the information to gauge quality, freshness, and applicability of master information
  • Establish master information Responsible, Accountable, Consulted, or Informed (RACI) models for owners, reviewers, and informed stakeholders.

Sometimes, we group this knowledge management work into other categories, like content management. However, information governance needs to also be inclusive of these activities; otherwise, how can we be successful? No one can live on donuts alone!

Does your information governance program include content management? Do you have comments about the quality of EIM user assistance (online help, PDFs, printed documentation, etc.)?

Comments

Tags:

awareness

Donuts, Content Management and Information Governance

Ina Felsheim

I was on vacation for two weeks, which was awesome, and my girls mainly wanted to do two things:

I had my own list of projects, too. The big one was installing glass tile on the kitchen backsplash. (Grout everywhere. That’s all I’m saying.)

After two weeks of glorious holiday, I sat down to take stock. The old technical writer in me came creeping out, and I began to count how many sets of instructions we followed over the course of the two weeks—more than 15, definitely. And the amazing thing? They were all right. Every. Last. One. From proper application of fabric paint to proper frying temperature for homemade donuts, to putting together a shoe rack that came in 20 pieces.

I’m pretty sure this wouldn’t have happened five years ago. The difference comes from an increased awareness in the importance of great user assistance. Without successful “use,” who’s going to evangelize your product?

Information Governance: Part of a Larger Food Pyramid

In EIM, we have a well-seasoned group of information developers. They apply information governance principles every day:

  • Create a single source of master information (in this case, product step-by-step instructions)
  • Manage versioning of master information (as product updates happen)
  • Survey end-users of the information to gauge quality, freshness, and applicability of master information
  • Establish master information Responsible, Accountable, Consulted, or Informed (RACI) models for owners, reviewers, and informed stakeholders.

Sometimes, we group this knowledge management work into other categories, like content management. However, information governance needs to also be inclusive of these activities; otherwise, how can we be successful? No one can live on donuts alone!

Does your information governance program include content management? Do you have comments about the quality of EIM user assistance (online help, PDFs, printed documentation, etc.)?

Comments

Andre Smith

About Andre Smith

An Internet, Marketing and E-Commerce specialist with several years of experience in the industry. He has watched as the world of online business has grown and adapted to new technologies, and he has made it his mission to help keep businesses informed and up to date.

Tags:

awareness

Donuts, Content Management and Information Governance

Ina Felsheim

I was on vacation for two weeks, which was awesome, and my girls mainly wanted to do two things:

I had my own list of projects, too. The big one was installing glass tile on the kitchen backsplash. (Grout everywhere. That’s all I’m saying.)

After two weeks of glorious holiday, I sat down to take stock. The old technical writer in me came creeping out, and I began to count how many sets of instructions we followed over the course of the two weeks—more than 15, definitely. And the amazing thing? They were all right. Every. Last. One. From proper application of fabric paint to proper frying temperature for homemade donuts, to putting together a shoe rack that came in 20 pieces.

I’m pretty sure this wouldn’t have happened five years ago. The difference comes from an increased awareness in the importance of great user assistance. Without successful “use,” who’s going to evangelize your product?

Information Governance: Part of a Larger Food Pyramid

In EIM, we have a well-seasoned group of information developers. They apply information governance principles every day:

  • Create a single source of master information (in this case, product step-by-step instructions)
  • Manage versioning of master information (as product updates happen)
  • Survey end-users of the information to gauge quality, freshness, and applicability of master information
  • Establish master information Responsible, Accountable, Consulted, or Informed (RACI) models for owners, reviewers, and informed stakeholders.

Sometimes, we group this knowledge management work into other categories, like content management. However, information governance needs to also be inclusive of these activities; otherwise, how can we be successful? No one can live on donuts alone!

Does your information governance program include content management? Do you have comments about the quality of EIM user assistance (online help, PDFs, printed documentation, etc.)?

Comments

Tags:

awareness

Donuts, Content Management and Information Governance

Ina Felsheim

I was on vacation for two weeks, which was awesome, and my girls mainly wanted to do two things:

I had my own list of projects, too. The big one was installing glass tile on the kitchen backsplash. (Grout everywhere. That’s all I’m saying.)

After two weeks of glorious holiday, I sat down to take stock. The old technical writer in me came creeping out, and I began to count how many sets of instructions we followed over the course of the two weeks—more than 15, definitely. And the amazing thing? They were all right. Every. Last. One. From proper application of fabric paint to proper frying temperature for homemade donuts, to putting together a shoe rack that came in 20 pieces.

I’m pretty sure this wouldn’t have happened five years ago. The difference comes from an increased awareness in the importance of great user assistance. Without successful “use,” who’s going to evangelize your product?

Information Governance: Part of a Larger Food Pyramid

In EIM, we have a well-seasoned group of information developers. They apply information governance principles every day:

  • Create a single source of master information (in this case, product step-by-step instructions)
  • Manage versioning of master information (as product updates happen)
  • Survey end-users of the information to gauge quality, freshness, and applicability of master information
  • Establish master information Responsible, Accountable, Consulted, or Informed (RACI) models for owners, reviewers, and informed stakeholders.

Sometimes, we group this knowledge management work into other categories, like content management. However, information governance needs to also be inclusive of these activities; otherwise, how can we be successful? No one can live on donuts alone!

Does your information governance program include content management? Do you have comments about the quality of EIM user assistance (online help, PDFs, printed documentation, etc.)?

Comments

Neil Patrick

About Neil Patrick

Neil Patrick is director of the GRC Center of Excellence in EMEA for SAP.

Tags:

awareness

Donuts, Content Management and Information Governance

Ina Felsheim

I was on vacation for two weeks, which was awesome, and my girls mainly wanted to do two things:

I had my own list of projects, too. The big one was installing glass tile on the kitchen backsplash. (Grout everywhere. That’s all I’m saying.)

After two weeks of glorious holiday, I sat down to take stock. The old technical writer in me came creeping out, and I began to count how many sets of instructions we followed over the course of the two weeks—more than 15, definitely. And the amazing thing? They were all right. Every. Last. One. From proper application of fabric paint to proper frying temperature for homemade donuts, to putting together a shoe rack that came in 20 pieces.

I’m pretty sure this wouldn’t have happened five years ago. The difference comes from an increased awareness in the importance of great user assistance. Without successful “use,” who’s going to evangelize your product?

Information Governance: Part of a Larger Food Pyramid

In EIM, we have a well-seasoned group of information developers. They apply information governance principles every day:

  • Create a single source of master information (in this case, product step-by-step instructions)
  • Manage versioning of master information (as product updates happen)
  • Survey end-users of the information to gauge quality, freshness, and applicability of master information
  • Establish master information Responsible, Accountable, Consulted, or Informed (RACI) models for owners, reviewers, and informed stakeholders.

Sometimes, we group this knowledge management work into other categories, like content management. However, information governance needs to also be inclusive of these activities; otherwise, how can we be successful? No one can live on donuts alone!

Does your information governance program include content management? Do you have comments about the quality of EIM user assistance (online help, PDFs, printed documentation, etc.)?

Comments

Tags:

awareness

Donuts, Content Management and Information Governance

Ina Felsheim

I was on vacation for two weeks, which was awesome, and my girls mainly wanted to do two things:

I had my own list of projects, too. The big one was installing glass tile on the kitchen backsplash. (Grout everywhere. That’s all I’m saying.)

After two weeks of glorious holiday, I sat down to take stock. The old technical writer in me came creeping out, and I began to count how many sets of instructions we followed over the course of the two weeks—more than 15, definitely. And the amazing thing? They were all right. Every. Last. One. From proper application of fabric paint to proper frying temperature for homemade donuts, to putting together a shoe rack that came in 20 pieces.

I’m pretty sure this wouldn’t have happened five years ago. The difference comes from an increased awareness in the importance of great user assistance. Without successful “use,” who’s going to evangelize your product?

Information Governance: Part of a Larger Food Pyramid

In EIM, we have a well-seasoned group of information developers. They apply information governance principles every day:

  • Create a single source of master information (in this case, product step-by-step instructions)
  • Manage versioning of master information (as product updates happen)
  • Survey end-users of the information to gauge quality, freshness, and applicability of master information
  • Establish master information Responsible, Accountable, Consulted, or Informed (RACI) models for owners, reviewers, and informed stakeholders.

Sometimes, we group this knowledge management work into other categories, like content management. However, information governance needs to also be inclusive of these activities; otherwise, how can we be successful? No one can live on donuts alone!

Does your information governance program include content management? Do you have comments about the quality of EIM user assistance (online help, PDFs, printed documentation, etc.)?

Comments

Tags:

awareness

Donuts, Content Management and Information Governance

Ina Felsheim

I was on vacation for two weeks, which was awesome, and my girls mainly wanted to do two things:

I had my own list of projects, too. The big one was installing glass tile on the kitchen backsplash. (Grout everywhere. That’s all I’m saying.)

After two weeks of glorious holiday, I sat down to take stock. The old technical writer in me came creeping out, and I began to count how many sets of instructions we followed over the course of the two weeks—more than 15, definitely. And the amazing thing? They were all right. Every. Last. One. From proper application of fabric paint to proper frying temperature for homemade donuts, to putting together a shoe rack that came in 20 pieces.

I’m pretty sure this wouldn’t have happened five years ago. The difference comes from an increased awareness in the importance of great user assistance. Without successful “use,” who’s going to evangelize your product?

Information Governance: Part of a Larger Food Pyramid

In EIM, we have a well-seasoned group of information developers. They apply information governance principles every day:

  • Create a single source of master information (in this case, product step-by-step instructions)
  • Manage versioning of master information (as product updates happen)
  • Survey end-users of the information to gauge quality, freshness, and applicability of master information
  • Establish master information Responsible, Accountable, Consulted, or Informed (RACI) models for owners, reviewers, and informed stakeholders.

Sometimes, we group this knowledge management work into other categories, like content management. However, information governance needs to also be inclusive of these activities; otherwise, how can we be successful? No one can live on donuts alone!

Does your information governance program include content management? Do you have comments about the quality of EIM user assistance (online help, PDFs, printed documentation, etc.)?

Comments

Ioana Sima

About Ioana Sima

Ioana Sima is an architecture student at Ion Mincu University of Architecture, CMO of DigitalWebProperties, coffee lover, and avid gamer. Despite my academic background, I decided to pursue a career in digital marketing. Why? Because it's thrilling, fascinating, and unpredictable. My goal is to contribute to the creation of something truly meaningful & to grow professionally. Follow me on Twitter if you enjoy gaming, dank memes, and digital marketing.

Tags:

awareness

Donuts, Content Management and Information Governance

Ina Felsheim

I was on vacation for two weeks, which was awesome, and my girls mainly wanted to do two things:

I had my own list of projects, too. The big one was installing glass tile on the kitchen backsplash. (Grout everywhere. That’s all I’m saying.)

After two weeks of glorious holiday, I sat down to take stock. The old technical writer in me came creeping out, and I began to count how many sets of instructions we followed over the course of the two weeks—more than 15, definitely. And the amazing thing? They were all right. Every. Last. One. From proper application of fabric paint to proper frying temperature for homemade donuts, to putting together a shoe rack that came in 20 pieces.

I’m pretty sure this wouldn’t have happened five years ago. The difference comes from an increased awareness in the importance of great user assistance. Without successful “use,” who’s going to evangelize your product?

Information Governance: Part of a Larger Food Pyramid

In EIM, we have a well-seasoned group of information developers. They apply information governance principles every day:

  • Create a single source of master information (in this case, product step-by-step instructions)
  • Manage versioning of master information (as product updates happen)
  • Survey end-users of the information to gauge quality, freshness, and applicability of master information
  • Establish master information Responsible, Accountable, Consulted, or Informed (RACI) models for owners, reviewers, and informed stakeholders.

Sometimes, we group this knowledge management work into other categories, like content management. However, information governance needs to also be inclusive of these activities; otherwise, how can we be successful? No one can live on donuts alone!

Does your information governance program include content management? Do you have comments about the quality of EIM user assistance (online help, PDFs, printed documentation, etc.)?

Comments

Bruce McCuaig

About Bruce McCuaig

Bruce McCuaig is director - Product Marketing at SAP GRC solutions. He is responsible for development and execution of the product marketing strategy for SAP Risk Management, SAP Audit Management and SAP solutions for three lines of defense. Bruce has extensive experience in industry as a finance professional, as a chief risk officer, and as a chief audit executive. He has written and spoken extensively on GRC topics and has worked with clients around the world implementing GRC solutions and technology.

Tags:

awareness

Donuts, Content Management and Information Governance

Ina Felsheim

I was on vacation for two weeks, which was awesome, and my girls mainly wanted to do two things:

I had my own list of projects, too. The big one was installing glass tile on the kitchen backsplash. (Grout everywhere. That’s all I’m saying.)

After two weeks of glorious holiday, I sat down to take stock. The old technical writer in me came creeping out, and I began to count how many sets of instructions we followed over the course of the two weeks—more than 15, definitely. And the amazing thing? They were all right. Every. Last. One. From proper application of fabric paint to proper frying temperature for homemade donuts, to putting together a shoe rack that came in 20 pieces.

I’m pretty sure this wouldn’t have happened five years ago. The difference comes from an increased awareness in the importance of great user assistance. Without successful “use,” who’s going to evangelize your product?

Information Governance: Part of a Larger Food Pyramid

In EIM, we have a well-seasoned group of information developers. They apply information governance principles every day:

  • Create a single source of master information (in this case, product step-by-step instructions)
  • Manage versioning of master information (as product updates happen)
  • Survey end-users of the information to gauge quality, freshness, and applicability of master information
  • Establish master information Responsible, Accountable, Consulted, or Informed (RACI) models for owners, reviewers, and informed stakeholders.

Sometimes, we group this knowledge management work into other categories, like content management. However, information governance needs to also be inclusive of these activities; otherwise, how can we be successful? No one can live on donuts alone!

Does your information governance program include content management? Do you have comments about the quality of EIM user assistance (online help, PDFs, printed documentation, etc.)?

Comments

Tags:

awareness

Donuts, Content Management and Information Governance

Ina Felsheim

I was on vacation for two weeks, which was awesome, and my girls mainly wanted to do two things:

I had my own list of projects, too. The big one was installing glass tile on the kitchen backsplash. (Grout everywhere. That’s all I’m saying.)

After two weeks of glorious holiday, I sat down to take stock. The old technical writer in me came creeping out, and I began to count how many sets of instructions we followed over the course of the two weeks—more than 15, definitely. And the amazing thing? They were all right. Every. Last. One. From proper application of fabric paint to proper frying temperature for homemade donuts, to putting together a shoe rack that came in 20 pieces.

I’m pretty sure this wouldn’t have happened five years ago. The difference comes from an increased awareness in the importance of great user assistance. Without successful “use,” who’s going to evangelize your product?

Information Governance: Part of a Larger Food Pyramid

In EIM, we have a well-seasoned group of information developers. They apply information governance principles every day:

  • Create a single source of master information (in this case, product step-by-step instructions)
  • Manage versioning of master information (as product updates happen)
  • Survey end-users of the information to gauge quality, freshness, and applicability of master information
  • Establish master information Responsible, Accountable, Consulted, or Informed (RACI) models for owners, reviewers, and informed stakeholders.

Sometimes, we group this knowledge management work into other categories, like content management. However, information governance needs to also be inclusive of these activities; otherwise, how can we be successful? No one can live on donuts alone!

Does your information governance program include content management? Do you have comments about the quality of EIM user assistance (online help, PDFs, printed documentation, etc.)?

Comments

Richard Howells

About Richard Howells

Richard Howells is a Vice President at SAP responsible for the positioning, messaging, AR , PR and go-to market activities for the SAP Supply Chain solutions.

Tags:

awareness