Create and compare an “Is Map” vs. a “Should Map.”

[Hailey MacCachren]

Is Map – what is the current process, how things are right now
Should Map – what a perfect process looks like, covers all needs of the business

[Wendie Balzano]

past, current future

[Alamin Ahmed]

now vs aspired

[Beverley Riley]

What it is now vs what it should or could be

[Calysta Smiley]

How you are currently running, vs how you’d like to be running.

[Doug Berglund]

The is Map is the current status of the environment and the should map is the ultimate KPA implementation that fulfills the goals for ITAM to the best achievable level.

[Patrick Pate]

Is Map: Current processes, tools, practices and people supporting ITAM

Should Map: Futured desired state of ITAM for the organization. What need to be built, improved or remediated.

[Milton Crawford]

Is Map is current, vs Should map is the future.

[Madhavi Poosala]

The “Is Map” focuses on assessing the current state of ITAM, identifying strengths, weaknesses, and areas for improvement.
The “Should Map” provides a vision for the future state of ITAM, outlining the desired improvements, best practices, and goals to strive for

[Roy Bonilla]

current and future

[Jennifer Fedyszyn]

One aspect of my organization’s “Is” and “Should” map (e.g., current state and future state):

Is: We are not doing the best job of documentation management, specific to the financials in our asset management system. Specifically, we receive quotes from a particular vendor with one line item (per the IT resources) and it isn’t broken down into software, hardware, and services.
Should: We should request, and enforce itemized quotes for better tracking, and set best practices for documentation management and data entry that are enforced and periodically audited to ensure accuracy.

[Eleusa Nunes]

N/A

[JerromeJade Rosales]

Is Map Should Map
Current state of processes and systems Desired future state and improvements
Existing workflows, resources, pain points Optimized workflows, ideal resources, goals
Understand existing challenges and inefficiencies Define objectives and visualize improvements
Baseline for analysis and improvement Roadmap for change and implementation
Identifies current roles and responsibilities Engages stakeholders in the vision for change

[Laura Hudani]

IS Map
Description: The current state of the ITAM workflow, showing how software licenses are managed today.

Procurement:
Individual departments often purchase software independently.
Limited oversight from central ITAM or Procurement teams.
Software is occasionally purchased without considering compliance or cost efficiency.

Asset Tracking:
A mix of spreadsheets and outdated tools is used to track licenses.
Data is incomplete and inconsistently updated.
Shadow IT purchases are not included in tracking.

Compliance:
Compliance checks are reactive, typically occurring during audits.
High risk of non-compliance due to poor visibility into usage and licensing.

Disposal:
Minimal efforts to track end-of-life for software.

[Laura Hudani]

IS Map
Description: The current state of the ITAM workflow, showing how software licenses are managed today.

Procurement:
Individual departments often purchase software independently.
Limited oversight from central ITAM or Procurement teams.
Software is occasionally purchased without considering compliance or cost efficiency.

Asset Tracking:
A mix of spreadsheets and outdated tools is used to track licenses.
Data is incomplete and inconsistently updated.
Shadow IT purchases are not included in tracking.

Compliance:
Compliance checks are reactive, typically occurring during audits.
High risk of non-compliance due to poor visibility into usage and licensing.

Disposal:
Minimal efforts to track end-of-life for software.

SHOULD Map
Description: The ideal state of the ITAM workflow, showing how software licenses should be managed.

Procurement:

All software acquisitions go through a centralized procurement process.
ITAM teams review and approve all purchases based on compliance and budget considerations.
Standardized software options are provided to streamline decision-making.
Asset Tracking:

A centralized ITAM system with automated discovery tools tracks all licenses in real time.
Shadow IT purchases are minimized through employee education and stricter policies.
License data is accurate, comprehensive, and easily accessible.
Compliance:

Regular compliance audits are proactively conducted.
Automated tools flag non-compliance risks and optimize usage.
Licenses are monitored to avoid over-purchasing or under-utilization.
Disposal:

Expired or unused licenses are systematically reclaimed and reallocated.
Clear processes are in place for decommissioning and retiring software.

[Author]

Posts