Skip to main content
Jalen Pickens

About

Three roles, in this order.

Jalen enters ambiguous or disorganized environments, identifies the real source of the problem, establishes structure, translates complexity, and helps organizations make better decisions.

Most environments do not lack effort. They lack an agreed account of what is actually true — which source is authoritative, who owns which decision, and what has already been decided. My work lives where technical systems and organizational reality collide.

The foundation is hands-on: networks, endpoints, identity, infrastructure, secure communications and mission systems kept running under operational pressure. Building and troubleshooting those systems is what makes later governance decisions credible.

Responsibility then widened into Information Assurance and cybersecurity support, RMF and authorization workflows, configuration, change and requirements management, systems integration, modernization, contractor coordination and project leadership.

Today the work sits at the intersection of technology, cybersecurity, operations, governance and project management: authoritative records, explicit owners, defined decision points, baselines, acceptance criteria and handoff controls, with constant translation among engineers, cybersecurity teams, contractors, mission owners and senior leaders.

I treat continuity as evidence that a capability truly exists. If the operation depends on who is in the room, it has not been built yet.

Archetype

Diagnostician → Strategist → Translator

The order matters more than the labels. Skipping the first role is the most common and most expensive mistake in transformation work.

  1. I

    Diagnostician

    Identify the real source of the problem.

    Before anything is promised, the actual problem is scoped and the evidence is collected. Most stated problems are symptoms of an unowned decision or an untrusted source.

  2. II

    Strategist

    Establish structure the organization can operate.

    Structure means requirements, ownership, decision points and an executable approach — sequenced so the organization can absorb the change while it still has to deliver.

  3. III

    Translator

    Make complexity legible to everyone who must act on it.

    Executives, engineers and operators are usually describing the same system three different ways. Holding one accurate account across all three is what keeps the work from splitting apart.

How I Lead the Work

Four operating principles.

Selected operating ideas that decide how an engagement is run, before any framework is chosen.

  1. A

    Diagnose before methodology

    Evaluate uncertainty, criticality, dependency structure, compliance exposure, reversibility and stakeholder availability before selecting predictive, adaptive or hybrid delivery. The question is always: what is fixed, what is uncertain, which decision is reversible, and what commitment will this create?

  2. B

    Make decisions inspectable

    Separate facts, assumptions, risks, options, authority and acceptance evidence. A decision anyone can re-read months later is worth more than a decision everyone agreed to quickly.

  3. C

    Lead across boundaries

    Role-specific communication, principled negotiation, cultural awareness, controlled transparency and evidence-based escalation. Engineers, security, resource owners and executives need the same truth in different forms.

  4. D

    Transfer the capability

    SOPs, job aids, controlled repositories, training, configuration baselines, recorded lessons and a planned operational handoff. A successful handoff is a deliverable, not an afterthought.

Leadership Philosophy

Evidence before ego.

  1. 01

    Evidence before ego.

  2. 02

    Decisions over meetings.

  3. 03

    Foundations before acceleration.

    “Don't start racing before you've tied your shoes.”

  4. 04

    Curiosity over assumption.

  5. 05

    Build for continuity.

  6. 06

    Leadership multiplies others.

Method

SAFER

The working method behind every engagement. Five stages, run in sequence.

State of the information

  1. Ambiguity
  2. Current state: Scoped problem
  3. Assessed evidence
  4. Formalized structure
  5. Controlled action
  6. Verified, transferable record

Stage 1 of 5 · S — Scope

What is the actual problem?

What is evaluated

  • The problem as stated
  • The boundaries around it
  • Objectives
  • What is known and unknown

Why it matters to the decision

Establishes which decision is actually required, before anything is promised.

Generalized example

A request arrives described as a tooling problem; scoping shows the decision required is who owns the record.

What it can produce

A stated problem, boundaries and objectives.

Where this stage is visible

Entering an unfamiliar organization and defining the actual problem before proposing anything.

Building an Operational SOP in One Month

What Holds It

Faith. Family. Service. Stewardship.

Before titles and credentials, I am a husband and father. Family keeps ambition in perspective and reminds me that leadership means stewardship—of people, opportunities, trust, and time.

  • Faith.
  • Family.
  • Service.
  • Stewardship.

Next

Have a complicated problem? Good.

Start a Conversation