The Executive Diagnostic and Governance Toolkit
Local Area Network Toolkit
Score your own local Area Network red, amber or green, find out which part is weakest, and walk into the next budget round able to defend what you want to fix.
Each order is checked and updated against the latest insights before delivery. That is why access takes up to 24 hours rather than being instant.
| 1 |
You stop guessing where you stand. You finish with a score, not an opinion: every part of your function rated red, amber or green, with the weakest ranked first. Evidence: a Quick Scan for the shape of it, then seven domain assessments of 30 scored questions each, 210 in all, rolled into one scorecard, plus a maturity radar and a current-versus-target gap analysis. |
| 2 |
You can defend the decision. You walk into the budget round with the gap named, the owner named and done defined, instead of a case built on instinct. Evidence: project charter, scope statement, RACI, requirements traceability and work breakdown structure, pre-filled in your domain's language. |
| 3 |
The work actually moves. The month after the decision is already built, so nothing stalls waiting for someone to design a form. Evidence: more than 60 project templates across all five PMBOK process groups, plus runbooks, SOPs, a KPI framework, audit checklists and a risk matrix. 55 to 65 files in total. |
| 4 |
You use it the day it lands. No blank templates to interpret. Every workbook opens with what it is, who uses it, when, how, a 1 to 5 scoring guide, what good looks like, and a worked example you delete and type over. |
The situation this is built for
Every budget cycle, you face the same challenge. Leadership wants to know why your Local Area Network needs attention now. They ask why you're upgrading switches instead of expanding Wi-Fi. You know the core network is fragile, but you can't prove it in a way that aligns with business risk. You end up reacting to outages instead of planning. You rely on tribal knowledge. You lack a structured way to assess hardware age, software patching cycles, or support response times. Without clear evidence, your requests get delayed or cut. You’re expected to lead, but you don’t have the tools to assess, rank, or defend.
Who this is for
A technical operations leader who owns the Local Area Network function across one or more sites. Responsible for uptime, user connectivity, hardware lifecycle, software compatibility, and onsite support coordination. Works with Windows environments daily and manages cross-functional teams during outages.
Who this is not for
This is not for network engineers focused only on configuration, nor for IT generalists managing wide area links. It is not for those who only install gear without owning outcomes. It is not for vendors selling tools or platforms.
What you walk away with
- Conduct a full maturity assessment of your Local Area Network
- Identify the top three technical debt areas draining team capacity
- Build a ranked roadmap with justification tied to business impact
- Present findings using evidence that resonates in leadership meetings
- Implement changes with a clear sequence and success metrics
How this maps to your situation
- Assessment
- Prioritization
- Defensibility
- Execution
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 3 hours per module, designed for weekly progress with team input. Most leaders complete the full assessment in 12 weeks.
How this compares to the alternatives
Unlike generic IT courses, this focuses exclusively on the Local Area Network function. It does not teach vendor-specific commands or sell tools. It provides a decision framework, not just knowledge. Compared to consultants, it builds internal capability and leaves you with documented evidence, not a one-time report.
Also included: the full course, for when you want the reasoning behind a finding (12 modules, 144 chapters)
Depth reference. The diagnostic and the templates stand on their own; this is what to read when you want the reasoning behind a finding.
- Mapping all physical and virtual network segments under your control
- Identifying dependencies on Windows domain services and login processes
- Documenting switch and router inventory by location and model
- Classifying connected devices by function and criticality
- Determining which user groups rely on each network segment
- Assessing cable plant age and topology documentation status
- Reviewing power and environmental conditions at network closets
- Logging firmware versions across switching infrastructure
- Tracking DHCP scope assignments and IP address management
- Evaluating VLAN segmentation for security and traffic control
- Measuring time since last full network topology update
- Creating a master inventory spreadsheet with ownership fields
- Calculating mean time between failures for each switch model
- Checking end-of-support dates for all active hardware units
- Reviewing spare parts availability and lead times
- Auditing power supply and fan failure logs over twelve months
- Measuring temperature trends in network equipment enclosures
- Assessing physical access controls at rack locations
- Documenting cable management practices at distribution points
- Evaluating stackable switch configurations for single points of failure
- Tracking replacement costs for aging hardware by site
- Validating compatibility of existing hardware with future needs
- Reviewing past hardware failure incidents and root causes
- Creating a five-year refresh timeline with cost projections
- Comparing running configurations across same-model switches
- Checking for default passwords or unsecured access methods
- Reviewing configuration backup frequency and storage locations
- Auditing SSH and console access control lists
- Verifying firmware signing and update validation processes
- Assessing use of centralized configuration management tools
- Measuring time to deploy a standard configuration to new devices
- Identifying undocumented configuration changes in change logs
- Checking consistency of logging and monitoring settings
- Evaluating access control list rules for unnecessary permissiveness
- Reviewing role-based access settings for network management
- Documenting configuration drift from baseline standards
- Collecting baseline round-trip time between critical subnets
- Measuring packet loss during peak business hours
- Tracking interface error rates on trunk links
- Assessing CPU and memory utilization trends on core switches
- Reviewing broadcast and multicast traffic levels
- Logging frequency of spanning tree recalculations
- Measuring failover times during planned reboots
- Auditing quality of service tagging implementation
- Evaluating jitter and latency for voice over IP traffic
- Checking buffer utilization during large file transfers
- Documenting frequency of user-reported slowness complaints
- Creating performance dashboards with historical benchmarks
- Reviewing port security settings on access switches
- Checking Dynamic Host Configuration Protocol snooping status
- Assessing VLAN hopping prevention measures
- Auditing 802.1X authentication deployment progress
- Measuring time to isolate compromised devices
- Reviewing firewall rule interactions with Local Area Network policies
- Evaluating guest network isolation from internal systems
- Checking rogue device detection capabilities
- Assessing logging of MAC address table changes
- Reviewing access control policies for contractor devices
- Measuring coverage of endpoint compliance checks
- Documenting response time to security alert escalations
- Measuring mean time to acknowledge network tickets
- Reviewing escalation paths for unresolved connectivity issues
- Auditing accuracy of problem categorization in ticketing system
- Assessing time required to access physical network locations
- Evaluating use of remote troubleshooting tools
- Tracking frequency of repeat incidents for same issue
- Measuring time to restore service after outage declaration
- Reviewing knowledge base article completeness for common fixes
- Assessing cross-training levels among support staff
- Documenting communication protocols during major incidents
- Evaluating post-mortem review quality and action follow-up
- Creating a support efficiency scorecard
- Measuring time to domain controller discovery at boot
- Reviewing Group Policy Object application delays
- Assessing DNS query success rates from client machines
- Auditing Kerberos authentication failure logs
- Evaluating impact of network latency on file server access
- Checking reliability of printer mapping over VLANs
- Measuring time to establish Remote Desktop sessions
- Reviewing Windows event log correlation with switch logs
- Assessing domain join success rate for new devices
- Documenting network-related causes of Windows updates failing
- Evaluating roaming profile load times across subnets
- Creating a dependency map between network zones and AD sites
- Projecting device growth by department over eighteen months
- Measuring peak bandwidth utilization per switch port
- Assessing headroom before link saturation occurs
- Reviewing plans for new software requiring higher throughput
- Evaluating impact of IoT device integration on switch ports
- Forecasting power and cooling needs for expanded closets
- Measuring available patch panel ports by location
- Assessing switch port density and uplink capacity ratios
- Reviewing cable certification for future 10GBase-T support
- Estimating fiber run requirements between new work areas
- Documenting current PoE budget usage and headroom
- Creating a capacity heat map by building and floor
- Assessing completeness of network topology diagrams
- Reviewing accuracy of IP address allocation records
- Auditing switch port to wall jack mapping documents
- Evaluating labeling standards for cables and devices
- Measuring time to locate configuration backups
- Assessing searchability of internal knowledge base
- Reviewing as-built documentation for recent changes
- Checking version control status of configuration files
- Evaluating network diagram update frequency
- Documenting standard operating procedures for common tasks
- Assessing onboarding materials for new team members
- Creating a documentation maturity score
- Mapping monitored devices in network management system
- Reviewing alert thresholds for interface downtime
- Assessing uptime tracking accuracy for core switches
- Checking coverage of environmental sensors in closets
- Evaluating alert fatigue from duplicate notifications
- Measuring time to receive first alert after simulated failure
- Reviewing escalation paths for unacknowledged alerts
- Auditing alert-to-ticket creation automation
- Assessing root cause accuracy in alert descriptions
- Documenting coverage gaps in monitoring scope
- Evaluating alert resolution time benchmarks
- Creating a monitoring effectiveness index
- Assigning business criticality to each network segment
- Measuring downtime cost per hour for key departments
- Evaluating frequency and duration of past outages
- Assessing risk of single points of failure in core design
- Reviewing insurance or compliance exposure from gaps
- Calculating user productivity loss from connectivity issues
- Measuring time to detect and isolate faults
- Assessing reputational risk from repeated failures
- Evaluating vendor support response time SLAs
- Documenting leadership visibility of current issues
- Creating a weighted scoring model for initiative ranking
- Building a one-page priority justification document
- Translating technical findings into risk language
- Building a one-page network health dashboard
- Creating before-and-after scenarios for proposed changes
- Measuring executive understanding of network dependencies
- Reviewing past presentation materials for clarity
- Assessing use of visual evidence in strategy reviews
- Documenting leadership questions from prior budget cycles
- Evaluating timing of updates relative to planning cycles
- Creating a glossary for non-technical stakeholders
- Measuring confidence in roadmap after review sessions
- Preparing for trade-off questions during funding requests
- Delivering a five-minute status update that drives decisions
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.
Thousands of organisations have bought from The Art of Service since 2000.