カテゴリー 全て - consensus - problem - solutions - analysis

によって Samkelisiwe Ngcobo 5年前.

106

Problem description toolbox

When tackling a complex issue, it is crucial to thoroughly research and describe the problem from various perspectives to ensure effective solutions. Utilizing tools like the Smart Map can aid in gathering factual information and applying lateral thinking techniques.

Problem description toolbox

Where next?

You can continue to develop this map without the Smart Map wizard by saving it as a normal Mindomo map.

When have a comprehensive description of the problem, you can move towards finding solutions. Consider a brainstorm as a next step, using the Brainstorming Toolbox Smart Map.

You can delete this topic from the saved map.

Where next?


You can continue to develop this map without the Smart Map wizard by saving it as a normal Mindomo map.

When have a comprehensive description of the problem, you can move towards finding solutions. Consider a brainstorm as a next step, using the Brainstorming Toolbox Smart Map.

Welcome

Researching and describing a problem clearly is the foundation for solving it. Solutions based on incomplete research or poor descriptions can often fail to reach the root causes.

This Smart Map helps you to research and describe a problem from a number of different angles. It contains a mix of factual information-gathering tools and lateral thinking techniques, to develop perspectives that can point towards solutions.

You can use this map individually and in collaboration with others. It is vital to get consensus on the actual problem you are facing, otherwise there may be no consensus on the solution. Putting the descriptions together in one place helps you to explain and agree upon the basis for finding and evaluating solutions.

You can delete this topic from the saved map.

Welcome, Guest


Researching and describing a problem clearly is the foundation for solving it. Solutions based on incomplete research or poor descriptions can often fail to reach the root causes.
This Smart Map helps you to research and describe a problem from a number of different angles. It contains a mix of factual information-gathering tools and lateral thinking techniques, to develop perspectives that can point towards solutions.
You can use this map individually and in collaboration with others. It is vital to get consensus on the actual problem you are facing, otherwise there may be no consensus on the solution. Putting the descriptions together in one place helps you to explain and agree upon the basis for finding and evaluating solutions.

Information security threats in the company

Name the problem


Identify the problem or issue in a few words and press Enter. This will become the title of your map.

Be the problem

Be the problem is a popular technique for understanding problems. It means developing a character for the problem and describing its nature as if it were a person.

Be the problem


'Be the problem' is a popular technique for understanding problems. It means developing a character for the problem and describing its nature as if it were a person.

Insight

Add an insight


Add a statement describing the problem as if it were a person.

Analogies

Can you find analogies for this problem?
The underlying characteristics of a problem can sometimes be clearer when it is taken out of context.

Analogies


Can you find analogies for this problem?
The underlying characteristics of a problem can sometimes be clearer when it is taken out of context.

What is it like?

What is 'Information security threats in the company' like?


Is 'Information security threats in the company' like anything else?

Six serving men

"Six Serving Men" is based on Rudyard Kipling's poem, which begins:

''I keep six honest serving men
(They taught me all I knew);
Their names are What and Why and When
And How and Where and Who.''


We can profile a problem and perhaps discover more about it by asking structured questions.

Six Serving Men


'Six Serving Men' is based on Rudyard Kipling's poem, which begins:

I keep six honest serving men
(They taught me all I knew);
Their names are What and Why and When
And How and Where and Who.


We can profile a problem and perhaps discover more about it by asking structured questions.

Who?
Who not?

Who does not cause 'Information security threats in the company'?


Who causes 'Information security threats in the company'?


Where?
Where not?

Where does 'Information security threats in the company' not happen?


Where does 'Information security threats in the company' happen?


How?
How not?

How does 'Information security threats in the company' not happen?


How does 'Information security threats in the company' happen?


When?
When not?

When does 'Information security threats in the company' not happen?


When does 'Information security threats in the company' happen?


Why?
Why not?

Why is 'Information security threats in the company' not a problem?


Why is 'Information security threats in the company' a problem?


What?

What not?

What does not cause 'Information security threats in the company'?


What causes 'Information security threats in the company'?


Impact analysis

Impact analysis looks at who is affected by the problem - what the consequences are, rather than the causes.

Impact analysis


Impact analysis looks at who is affected by the problem - what the consequences are, rather than the causes.

Person

Who is affected?


Type in a name or role of someone who is affected by 'Information security threats in the company'

Impact

What is the impact?


How is Person affected by 'Information security threats in the company'?


Rate the impact by clicking an icon:

High impact - significant consequences

Medium impact - annoying but tolerable

Low impact - negligible effect

Root cause analysis

For analytical problems, root cause analysis can help to unravel indirect causes of problems, leading to more effective solutions. One way to do this is to keep asking "Why?" down to five levels, to understand the reasons behind the reasons.

Root Cause analysis


For analytical problems, root cause analysis can help to unravel indirect causes of problems, leading to more effective solutions. One way to do this is to keep asking 'Why?' down to five levels, to understand the reasons behind the reasons.

Cause

Why does 'Information security threats in the company' happen?


Enter a reason that 'Information security threats in the company' happens.

Why does 'Cause' happen?


Enter a reason that 'Cause' happens.
(Level 2 of 5)

Why does 'Cause' happen?


Enter a reason that 'Cause' happens.
(Level 3 of 5)

Why does 'Cause' happen?


Enter a reason that 'Cause' happens.
(Level 4 of 5)

Why does 'Cause' happen?


Enter a reason that 'Cause' happens.
(Level 5 of 5)

Solution criteria

How will you know when you have solved the problem?
* What will a successful resolution look like?
* How will you filter and assess potential solutions?
* How will you verify that the issue has been solved?
You might want to return to the solution criteria several times as you develop the definition of the problem.

Solution criteria


How will you know when you have solved 'Information security threats in the company'?

You might want to return to the solution criteria several times as you develop the definition of the problem.

Malware scanning software can identify potentially dangerous malware programs in email attachments and block users from downloading them in the first place.
Bring-your-own-device (BYOD) policies help set the ground rules and how employees can use personal devices at work. These rules can help protect a business from being compromised by unprotected personal devices.
Educating employees about the risk of malware can do a lot to prevent them from accidentally downloading ransomware.
By limiting each employee’s access to only the specific resources they need to do their job, organizations can minimize the impact of a breach that occurs when an employee account is misused.

Add solution criterion


Add a solution criterion. Make sure you consider:

What assumptions are you making?

In identifying the problem and the probability of a solution, what assumptions are you making?

Assumptions can sometimes be hard to see or accept. For example, if the "problem" is that sales of a certain product are too low, you may naturally aim to increase sales. You are ''assuming'' that the market demand for this product will continue. But if the demand disappeared overnight in a storm of negative publicity, then the original problem and solution also change. So the problem and logical solution are partly based on an assumption.

What assumptions are you making?


In identifying the problem and the probability of a solution, what assumptions are you making?

Assumptions can sometimes be hard to see or accept. For example, if the 'problem' is that sales of a certain product are too low, you may naturally aim to increase sales. You are assuming that the market demand for this product will continue. But if the demand disappeared overnight in a storm of negative publicity, then the original problem and solution also change. So the problem and logical solution are partly based on an assumption.

Assumption

Add an assumption


Identify an assumption you are making in both the description of the problem and the logical solution.

What don't you know?

What other information might help, but is not available today?
* How would it help?
* How could you obtain it?
* Can you work without it?
* What are the risks or consequences of not knowing?
* Who else might have further information and insight?

What don't you know?


What other information might help, but is not available today?

Hactivists
Cyberterrorists
Brokers
Cybercriminals

Add an unknown factor


Identify information or data that is not known or not reliable, and what you can do to find it. Think about:

What do you know?

Factual data about the problem

What do you know?


What factual data do you already have about 'Information security threats in the company'?

Bringing compromised USB drives or other personal devices to work
Visiting malware-laden websites
Former employees who thinks that accumulated data belongs to them not the organisation.
Former employees who have demoted to fired within the organisation.
Employees selling information to Media or outsiders.
Attacks are the result of employees intentionally misusing their user credentials.

Add a piece of data


Add an item of data or a reference to it. Think about:

Problem type

Whether this is mainly a creative or analytical problem

What type of problem is this?


Is 'Information security threats in the company' a creative issue or an analytical one?

Insiders (Employees)

Describe the problem type


Select the problem type or enter your own description.

Create something newChange somethingFix something broken