Technology Transformation Leader
JALEN PICKENS
I find the source of truth.
Program Delivery • Requirements & Configuration Governance • Decision Intelligence • Emerging Technology
Germany / Europe • Global Perspective
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
What I Solve
Four problems that look different and are not.
- 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.
- 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.
- 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.
- 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
Governed at scale.
- 2,000+
- Service / configuration actions governed
- ~200
- C4I/IT initiatives
- 250+
- Technical reviews facilitated
- 150+
- Personnel trained
Selected Transformations
Written accounts, not case-study marketing.
Selected work has been generalized to protect operational, customer, technical, and security-sensitive information.
- 01Read →
From Tribal Knowledge to Governed Operations
Requirements & Configuration Governance
An immature requirements and configuration capability moved toward a documented, repeatable operation that could be transferred to follow-on personnel.
- 02Read →
Reconstructing Ground Truth
Data Lineage & Asset Visibility
When the enterprise tool of record could no longer be depended upon, ground truth was rebuilt from authoritative technical sources rather than assumed from local records.
- 03Read →
Building an Operational SOP in One Month
Rapid Diagnosis & Process Formalization
Entering an unfamiliar organization, learning quickly, and formalizing an undocumented process into documentation the organization adopted.
Method
SAFER
A sequence, not a framework diagram. Each stage has to be finished before the next one earns the right to start.
Stage 1 of 5 · S — Scope
What is the actual problem?
- Define the actual problem
- Clarify boundaries
- Identify objectives
- Determine what is known and unknown
Proof
Stated plainly.
- Discipline
- Requirements & Configuration Governance
- Certification
- PMP · ITIL Foundation v5
- Delivery
- Greenfield → Operational
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.