Skip to main content
Jalen Pickens

Technology Transformation Leader

JALEN PICKENS

I find the source of truth.

Program Delivery • Requirements & Configuration Governance • Decision Intelligence • Emerging Technology

Worked in Europe, USA, and South Korea • Global Perspective

Explore My WorkExecutive Resume
Professional portrait of Jalen Pickens.
JALEN PICKENS — Technology Transformation Leader

In 90 Seconds

The short version.

Everything below expands on this. Nothing below contradicts it.

  1. 01Identity

    Jalen Pickens, a technology transformation leader who finds the source of truth and turns ambiguous, undocumented environments into governed, transferable operations.

  2. 02Problem

    The work begins where an organization cannot agree on what is true: undocumented practice, competing records, unclear ownership, and complexity nobody can explain to the people funding it.

  3. 03Scale

    2,000+ service/configuration actions governed. Every figure is traced further down this page.

  4. 04Method

    SAFER: Scope, Assess, Formalize, Execute & Verify, Record. Each stage has to be finished before the next one earns the right to start.

  5. 05Proof

    Written accounts of real programs, generalized to protect sensitive information but structured so the problem, the decision and the verification stay visible.

    Read the case studies
  6. 06Technical credibility

    Requirements and configuration governance, data lineage, infrastructure delivery and the platforms behind them — with direct experience separated from working familiarity. PMP and ITIL Foundation v5, CASP+, a Master's degree and a Bachelor's degree.

    ExperienceCredentials
  7. 07Current thinking

    Published notes cite their source, state the evidence boundary and say plainly what remains uncertain.

    Read Signals
  8. 08Action

    Start with the work, the record, or a conversation.

    Case studiesRésuméContact

Start where it matters to you

Position

Structure where there was none.

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

Diagnostician → Strategist → Translator

Philosophy

The source of truth.

Most transformation problems begin before implementation. They begin when an organization cannot agree on what is true.

Request

unverified

System Record

conflicting

Technical Record

stale

Stakeholder Input

owner unknown

Approved Baseline

incomplete

Authoritative state

One account, and the reason it holds.

Facts

Assumptions

Risks

Authority

  1. 01Sequence
  2. 02Ownership
  3. 03Baseline
  4. 04Change record

Verified record

One state. Checked, recorded, transferable.

Step 1 of 7 — Multiple Sources

What accounts of the truth exist?

Several records describe the same reality and none of them agree. Nothing can be decided yet, because nothing has been established.

Request

unverified

System Record

conflicting

Technical Record

stale

Stakeholder Input

owner unknown

Approved Baseline

incomplete

Authoritative state

One account, and the reason it holds.

Facts

Assumptions

Risks

Authority

  1. 01Sequence
  2. 02Ownership
  3. 03Baseline
  4. 04Change record

Verified record

One state. Checked, recorded, transferable.

Step 2 of 7 — Evidence Assessment

What does each source actually prove?

Each account is examined for what it can demonstrate, who owns it, and which decisions it is permitted to support.

Request

owner named

System Record

owner named

Technical Record

owner named

Stakeholder Input

owner named

Approved Baseline

owner named

Authoritative state

One account, and the reason it holds.

Facts

Assumptions

Risks

Authority

  1. 01Sequence
  2. 02Ownership
  3. 03Baseline
  4. 04Change record

Verified record

One state. Checked, recorded, transferable.

Step 3 of 7 — Discrepancy & Confidence

Where do they disagree, and how sure can we be?

Conflicts are recorded rather than quietly resolved in favour of the most convenient entry. Where confidence is low, it is stated.

Request

confidence: high

System Record

confidence: low

Technical Record

confidence: high

Stakeholder Input

confidence: medium

Approved Baseline

confidence: medium

Authoritative state

One account, and the reason it holds.

Facts

Assumptions

Risks

Authority

  1. 01Sequence
  2. 02Ownership
  3. 03Baseline
  4. 04Change record

Verified record

One state. Checked, recorded, transferable.

Step 4 of 7 — Authoritative State

Which account is now the one we work from?

One account becomes authoritative, and the reason it is authoritative travels with it.

Request

reconciled

System Record

reconciled

Technical Record

reconciled

Stakeholder Input

reconciled

Approved Baseline

reconciled

Authoritative state

One account, and the reason it holds.

Facts

Assumptions

Risks

Authority

  1. 01Sequence
  2. 02Ownership
  3. 03Baseline
  4. 04Change record

Verified record

One state. Checked, recorded, transferable.

Step 5 of 7 — Decision

Who decides, and on what basis?

Facts, assumptions, risks, options and authority are separated so the decision can be re-read months later and still make sense.

Request

reconciled

System Record

reconciled

Technical Record

reconciled

Stakeholder Input

reconciled

Approved Baseline

reconciled

Authoritative state

One account, and the reason it holds.

Facts

Assumptions

Risks

Authority

  1. 01Sequence
  2. 02Ownership
  3. 03Baseline
  4. 04Change record

Verified record

One state. Checked, recorded, transferable.

Step 6 of 7 — Controlled Implementation

How does the change happen without losing control?

The change moves through owned, sequenced steps against a known baseline instead of drifting away from it.

Request

reconciled

System Record

reconciled

Technical Record

reconciled

Stakeholder Input

reconciled

Approved Baseline

reconciled

Authoritative state

One account, and the reason it holds.

Facts

Assumptions

Risks

Authority

  1. 01Sequence
  2. 02Ownership
  3. 03Baseline
  4. 04Change record

Verified record

One state. Checked, recorded, transferable.

Step 7 of 7 — Verified Outcome

How do we know it is true now?

The end state is checked, recorded and made transferable, so the answer survives the people who produced it.

What I Solve

Four problems that look different and are not.

  1. 01

    There is no single authoritative source

    Multiple systems and records disagree, and nobody can say which one to trust. The work is to establish authoritative sources and the evidence behind them.

  2. 02

    The process lives in people's memory

    Undocumented practice, tribal knowledge and weak continuity. The work is to formalize the process so it survives personnel change.

  3. 03

    Ownership and decisions are unclear

    Work stalls between functions because no decision point or owner is defined. The work is to establish both, plainly, and record them.

  4. 04

    Complexity cannot be explained to the people funding it

    Technical reality and executive understanding have drifted apart. The work is one shared, evidenced account both audiences can act on.

Evidence of Practice

Every figure, traced.

Select a figure to follow its lineage. Each stop states exactly what the relationship is, and a lineage stops where the record stops.

Lineage · 2,000+

Service / configuration actions governed. Each stop below states what the relationship is. Only stops marked supported by or illustrated by carry evidential weight, and they carry only the weight the wording claims.

  1. Originates from

    2024–2026 · Enterprise Requirements & Configuration Governance

    The chapter the figure is drawn from, stated as scope of work rather than as an outcome claim.

    Read the chapter
  2. Illustrated by

    From Tribal Knowledge to Governed Operations

    The written account demonstrates the governance method behind work at this scale. It is the method, not the arithmetic, that the account evidences.

    SAFER visible: F — Formalize · E — Execute & Verify · R — Record

    Read the account
  3. Related context

    Requirements and configuration governance environment

    Korea / Indo-Pacific, 2024–2026. Context for the work; it does not itself substantiate the figure.

    See environments supported

Selected Transformations

Written accounts, not case-study marketing.

Selected work has been generalized to protect operational, customer, technical, and security-sensitive information.

Method

SAFER

A sequence, not a framework diagram. Each stage has to be finished before the next one earns the right to start.

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

How I Think

A problem arrives badly described.

A generalized walkthrough of how I work a problem. No client, no program, no outcome claimed — only the sequence.

The situation

Two systems of record disagree about what is deployed, and a decision is due. Nobody can say which record is authoritative.

Step 1 of 5

What is the actual problem?

Separate the disagreement from the decision that depends on it. Establish what must be true for the decision to be made at all.

Resulting artifact
A written problem statement with boundaries and open questions.

The point is not that the answer is right. The point is that the decision is inspectable — anyone can see what it rested on.

Proof

Stated plainly.

Currently Thinking About

The most recent note.

Signals is where I work through developments that change how technology should be governed.

AI · Agentic Systems · Cybersecurity · AI Governance · Program Management · Source: Reuters

The Agent Didn’t Need a Command Center

Authorization boundaries should cover what an agent can leave behind, not only what it can do in session.

corroboratedReported / attribution disputed
Read the full note →

Next

Have a complicated problem? Good.

The work worth doing usually starts with a problem nobody has been able to describe cleanly. Describe it badly — that is enough to begin.

Set Up a Conversation on LinkedInStart a Conversation