Skip to content
TECHNOLOGY IMPROVEMENT PROJECTS

Turn the roadmap into completed work.

Knowing what should improve is only useful if somebody owns the change.

Baselayer scopes and leads defined technology projects that strengthen the environment, simplify operations or remove problems the business has been carrying for too long.

We can deliver directly, coordinate existing suppliers or bring in specialist capability where needed.

DEFINE · DESIGN · DELIVER · VALIDATE · HANDOVER
Good project work should leave the environment easier to run.

Improvement projects start with a business outcome.

The objective is not to install technology for the sake of installing technology.

A project should answer a clear problem such as:

access is difficult to control
staff devices are inconsistent
Microsoft 365 has grown without structure
systems do not integrate properly
multiple suppliers own overlapping pieces of the environment
technology documentation is incomplete
network or connectivity reliability is affecting operations
onboarding and offboarding are inconsistent
an ageing platform needs to be replaced
a new site, team or acquisition needs to be integrated
COMMON PROJECT AREAS

The work depends on the environment.

Microsoft 365 improvement

Identity, administration, Teams, SharePoint, security configuration, licensing and operating structure.

Identity and access

MFA, privileged access, role design, joiner/mover/leaver processes and administrative account structure.

Endpoint and device management

Standardisation, device enrolment, management tooling, patching visibility and lifecycle improvement.

Network and connectivity

Business internet, redundancy, Wi-Fi, switching, firewall and site connectivity improvements.

Business systems

Platform selection, replacement, consolidation, configuration and integration projects.

Supplier consolidation

Reduce unnecessary overlap between technology providers, licences and services.

Technology documentation

Create the registers, diagrams, ownership records and operating documentation required to manage the environment properly.

Operating model improvement

Clarify how support, suppliers, technology decisions, risk and improvement work should be managed.

Use the right delivery model for the project.

This is particularly useful when several suppliers are involved but nobody inside the business has the time or technical breadth to coordinate the entire outcome.

BASELAYER CAN
define the requirement
write the scope
compare options
coordinate suppliers
lead implementation
manage dependencies
validate completion
document ownership
hand the completed environment back to the appropriate operational team

HOW PROJECTS WORK

01

Define

Agree on the problem, desired outcome, boundaries and key dependencies.

02

Design

Confirm the proposed solution, responsibilities, risks and implementation approach.

03

Deliver

Execute the work directly or coordinate the required internal and external resources.

04

Validate

Confirm the solution is operating as intended and that key risks or gaps have been addressed.

05

Handover

Document the environment and make ongoing ownership clear.

Good project work should leave the environment easier to run.

A project is not complete because the technical change happened.

THE BUSINESS SHOULD ALSO KNOW
what changed
why it changed
who now owns it
how it should be maintained
what documentation exists
what remaining risks are accepted
what should happen next

That is part of the delivery.

Have a technology problem that needs somebody to own it?