Scribd
Upload
15 views2 pages

Lec 2-Public Innovation

The document outlines the process of identifying problems in information systems, emphasizing observation, feedback collection, performance metrics, and recognizing common signs of issues. It stresses the importance of clearly documenting problems using the '5W1H' technique and includes tips for defining the scope and impact. Additionally, it discusses analyzing problems to assign system roles and responsibilities, culminating in the creation of a Responsibility Matrix (RACI) to clarify task ownership.

Uploaded by

sharjeelshafiq59
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
15 views2 pages

Lec 2-Public Innovation

The document outlines the process of identifying problems in information systems, emphasizing observation, feedback collection, performance metrics, and recognizing common signs of issues. It stresses the importance of clearly documenting problems using the '5W1H' technique and includes tips for defining the scope and impact. Additionally, it discusses analyzing problems to assign system roles and responsibilities, culminating in the creation of a Responsibility Matrix (RACI) to clarify task ownership.

Uploaded by

sharjeelshafiq59
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

MIS: Identifying Problems

1. Problem Identification
The first and most crucial step in developing an effective information system.

How to Identify a Problem:


- Observation: Watch how current systems/processes are working.

- Feedback Collection: Talk to stakeholders (employees, managers, users).

- Performance Metrics: Analyze reports, KPIs, or logs for inconsistencies or delays.

- Pain Points: Look for areas where:

- Tasks take longer than expected.


- Errors frequently occur.
- Communication gaps are evident.
- Manual effort is high and repetitive.

Common Signs of a Problem:


- Complaints from users

- Delays in decision-making

- Data duplication or inconsistency

- Increased operational costs

- Poor user experience

2. Writing Down the Problem


Writing the problem down clearly helps in understanding the scope and impact.

Tips for Documentation:


- State the Problem Clearly: Avoid jargon; be specific.

- Use the “5W1H” Technique:

- What is the problem?


- Where is it happening?
- When does it occur?
- Why is it a problem?
- Who is affected?
- How is it currently handled?
- Include Evidence: Screenshots, reports, statistics, or user feedback.

- Define Scope: Mention how widespread or critical the problem is.

3. Analyzing the Problem to Identify System Roles & Responsibilities


Once the problem is clearly stated, you can define what the system needs to do, and who
will be responsible.

From Problem → System Roles:


- Break down the problem into tasks or processes that a system can solve.
- Example: If the issue is "manual data entry errors," the system role might be "automated
data validation."

From Tasks → Assign Roles & Responsibili es:


- Identify stakeholders: Admins, Users, Managers, IT team, etc.

- Assign system responsibilities:


- Who will input data?
- Who will validate/approve it?
- Who maintains the system?
- Who uses the reports or outcomes?

Create a Responsibility Matrix (RACI):


- R – Responsible: Person who performs the task.

- A – Accountable: Person who makes final decisions and owns the process.

- C – Consulted: People who provide input.

- I – Informed: People who need to be kept updated.

You might also like