PUBLIC BETA
WWH · A SYSTEMS-THINKING FRAMEWORK FOR IT
WHATit is.
WHYit matters.
HOWit works.

A framework for understanding technology end to end.

Understand the technology itself. Examine why it exists, what problem it solves and why it matters. Then follow how it operates: from architecture and implementation through validation, failure, troubleshooting and recovery.

Hi, I’m Sathish, an IT infrastructure and systems professional. My work and curiosity span endpoints, systems, networks, identity, storage, cloud, security, operations and automation.

Public beta: useful now and continuing to improve through testing, review and feedback.

END-TO-END IT FLOW
W W H
EndpointHardware · OS · Apps
IdentityAccess · Policy · Trust
NetworkLAN · WAN · Wi‑Fi
InfrastructureCompute · Servers · Services
Cloud & DataStorage · SaaS · Hybrid
Operations & AutomationMonitor · Support · Improve
SECURITY · GOVERNANCE · RESILIENCE ACROSS ALL LAYERS
01 / FRAMEWORK BREAKDOWN

The three questions behind WWH.

WWH begins simply, then expands as far as the technology or problem requires. Each question reveals a different layer of understanding.

W

WHAT: Understand the system.

Definition, components, architecture, capabilities, dependencies and boundaries.

  • What is it?
  • What does it do?
  • What is it made of?
  • What does it depend on?
W

WHY: Understand the reason.

Purpose, problem, business value, technical reasoning, trade-offs and failure consequences.

  • Why does it exist?
  • What problem does it solve?
  • Why this design?
  • What happens if it fails?
H

HOW: Understand the operation.

Workflow, implementation, administration, validation, troubleshooting, recovery and improvement.

  • How does it work?
  • How is it implemented?
  • How do we verify it?
  • How do we recover?
02 / WWH IN ACTION

One concept. Three questions.

A simple DHCP example shows how WHAT → WHY → HOW turns a technology into a clear mental model.

EXAMPLE CONCEPT

DHCP

Start simple. Go deeper when needed.

WHAT What is DHCP? +
DHCP automatically gives devices the network settings they need, such as an IP address, subnet mask, default gateway and DNS servers.
WHY Why do we use DHCP? +
Without DHCP, administrators would have to configure network settings manually on many devices. DHCP saves time, reduces mistakes and makes changes easier to manage.
HOW How does DHCP work? +
A device asks the network for configuration. A DHCP server offers settings, the device requests them, and the server confirms the lease, commonly summarized as Discover → Offer → Request → Acknowledge (DORA).
03 / The IT landscape

One framework. The whole IT landscape.

Products change. Architecture, dependencies and troubleshooting logic remain. I look at IT as a connected system rather than a collection of isolated tools.

Endpoints & OS

Hardware, operating systems, applications, users and device lifecycle.

Where the user experience begins.

Identity & Access

Directory, authentication, authorization, policy and trust.

Who can do what, and why.

Networks

Switching, routing, wireless, DNS, DHCP, firewalls and traffic.

The path connecting every other layer.

Compute & Servers

Server operating systems, workloads, services and virtualization.

The shared capabilities underneath the business.

Data & Storage

Databases, capacity, retention, backup and recovery.

Where state, history and resilience live.

Cloud & SaaS

Cloud services, productivity, identity and hybrid integration.

Extending the architecture beyond the local stack.

Security & Operations

Hardening, monitoring, ITSM, documentation, change and recovery.

Keeping the system trustworthy and supportable.

Automation & AI

PowerShell, scripts, APIs, AI-assisted workflows and emerging agents.

Turning understood logic into repeatable action.
WWH IT FIELD GUIDE

The framework explains how the pieces connect. The Field Guide collects useful tools, commands, PowerShell, logs and references for working with them.

Explore the Field Guide →
04 / Journey

Curiosity that kept widening.

Not a claim to know everything. A career shaped by continually moving deeper and wider through IT.

EARLY

Repair & Fix

PCs · OS issues · hardware curiosity

FOUNDATION

Support

Users · endpoints · applications

EXPAND

Connect

Networks · Wi‑Fi · shared services

BUILD

Administer

Servers · identity · storage

OPERATE

Integrate

Enterprise systems · vendors · services

NOW

Automate

Scripts · APIs · AI-assisted workflows

05 / Sathish Kumar Velu

From fixing PCs to thinking in architectures.

IT infrastructure and systems professional with over a decade of hands-on experience across user support, endpoints, networks, servers, identity, storage, cloud services and enterprise operations.

Broad exposure. Honest depth. I strongly believe no one knows everything, and everyone knows something. Not knowing is not the problem; what matters is how you connect what you already understand to what you don’t, ask better questions, and test and validate until the unknown becomes understood.

WWH first. Everything else follows.

sathish@wwhsathish.com