Consultant to Creator: How My Career in IT Shaped My Writing Discipline

Consultant to Creator: How My Career in IT Shaped My Writing Discipline

Transitioning from over twenty years as an international computer consultant across Europe, Asia, and the Americas into publishing fiction might look like a sharp pivot from the outside. One world deals in system architectures, legacy code, and project delivery; the other deals in atmospheric magic, emotional arcs, and world-building.

In reality, the underlying discipline is identical.

Managing a deep, multi-series catalog of over twenty books doesn't happen through raw creative chaos. It relies on the exact same project management principles, system logic, and diagnostic troubleshooting I used when consulting on enterprise IT systems.

Here is how two decades in the tech industry hard-coded my writing discipline and shaped my approach to the creative craft.

1. The Systems Architecture: World-Building First

In IT consultancy, you never start writing code on day one. If you build a database or launch a project without a comprehensive system blueprint, the entire infrastructure will collapse under its own weight the moment it scales.

I treat fantasy and historical fiction with the exact same architectural rigor:

• The Master Codex: Before writing Chapter One, the rules of the universe are fully compiled into a Series Bible using story engines like Novelcrafter.

• Hard-Coded Constraints: Magic systems, mechanical relics, and historical limitations aren't adjusted on a whim to fix a plot hole. They are given strict inputs, outputs, and costs. Establishing firm guardrails up front prevents systemic plot errors later in the series.

2. The Project Manager’s Blueprint: 40,000-Word Movements

A massive IT deployment is never tackled as a single monolithic block; it is broken down into modular sprints, milestones, and deliverables.

[ THE IT-TO-PROSE PRODUCTION PIPELINE ]
+-------------------------------------------------+
| 1. SYSTEM SCOPING: Series Bibles & Lore Maps |
+-------------------------------------------------+
|
v
+-------------------------------------------------+
| 2. MODULAR SPRINTS: Four 10,000-word movements |
| composing a 40,000-word episodic unit. |
+-------------------------------------------------+
|
v
+-------------------------------------------------+
| 3. QUALITY ASSURANCE: Diagnostic editing, |
| pacing audits, and backlist tracking. |
+-------------------------------------------------+

When approaching a long-form novel or an episodic series, I apply my 10 Hour Project Manager framework directly to the writing schedule. By standardizing installments around modular 40,000-word targets, a massive catalog becomes predictable and manageable:

• Break Down the Scope: The total word count is segmented into four 10,000-word movements.

• Track the Velocity: Daily progress is logged in centralized Google Sheets to monitor output density and keep release schedules on target without burnout.

3. Debugging Broken Scenes: Logic Over Emotion

When an enterprise program throws an error, a consultant doesn't stare at the screen waiting for emotional inspiration; they run a diagnostic scan to find the exact line where the logic broke down.

When a drafted scene stalls, I treat it as a system error rather than "writer's block":

• Isolate the Bug: Is the character acting against their established internal code? Is the scene lacking a physical constraint? Is there unnecessary fluff muddying the dialogue?

• Strip the Waste: Using the same "minimum viable prose" discipline I learned programming microcomputers like the Acorn Atom in 1980, I strip the scene down to its bare structural bones, fix the logical flaw, and re-compile the narrative.

The Technician’s Advantage

Creativity provides the spark, the characters, and the atmosphere, but discipline provides the delivery system. Treating the writing studio like a well-oiled consultancy workshop ensures that stories aren't just started—they are engineered, polished, and delivered across the finish line for readers to enjoy.