CyberDesk Awareness
Information Responsibility Series
Welcome back to our Information Responsibility Series, where we are exploring practical principles that guide how information and workplace resources should be handled responsibly.
Last week, we discussed the Principle of Need to Know; accessing and sharing information based on your role and responsibilities.
This week, we move to the next important topic: The Principle of Need to Have.
While need to know focuses on information relevance, need to have focuses on what you actually require to perform your work effectively.
What Does “Need to Have” Mean?
The principle of need to have means that you should only request, retain, or use the tools, documents, devices, applications, and access that are necessary for your role and current responsibilities.
In simple terms, ask yourself:
Do I really need this to carry out my work?
This applies to:
- System access and permissions
- Shared folders and drives
- Applications and software tools
- Reports and documents
- Devices and work resources
The goal is to ensure that access and resources remain purposeful, relevant, and aligned with your responsibilities.
Why This Principle Matters
Having access to more than what is required can lead to:
- Unnecessary complexity
- Confusion over responsibilities
- Cluttered work environments
- Reduced accountability
- Misuse of resources
- Inefficient collaboration
When every user has only what they need, work becomes more focused, manageable, and easier to control.
This principle also helps departments manage resources effectively and ensure that tools and access are aligned with operational needs.
How This Applies to You
This principle applies to everyday workplace situations.
Access to Systems and Folders
Request access only to the applications, systems, or folders required for your role.
Software and Tools
Use only approved tools necessary for your daily tasks. Avoid requesting or installing tools that are not relevant to your responsibilities.
Documents and Reports
Retain only the files and reports required for your work rather than keeping multiple unnecessary copies.
Meetings and Distribution Lists
Be included only in meetings, mailing lists, and shared workspaces relevant to your role.
Common Habits to Avoid
- Requesting broad access “just in case”
- Keeping tools or permissions no longer required
- Retaining multiple copies of documents unnecessarily
- Staying in distribution groups unrelated to your current responsibilities
- Holding on to old resources after a change in role
These habits can create unnecessary clutter and reduce operational efficiency.
Best Practice
Before requesting access, tools, or documents, ask yourself:
Do I need this to perform my current task or role?
Will this resource directly support my work output?
If not, it may not be necessary to have it.
Coming Up Next in This Series
In our next edition, we will cover the final topic in this series:
Principle of Need to Keep
Why only necessary information, documents, and resources should be retained and how proper housekeeping supports efficiency.
Final Reminder
The principle of need to have is about purpose, relevance, and efficiency.
Having only what you need helps you work more effectively, keeps resources organized, and supports a smarter workplace.
