Our sources

Influences

Pineland OS is built from what practitioners are proving in the field. These are the programs, operators, and tools shaping how we build, and the specific lesson we took from each.

Influences, not affiliations. We credit ideas where they come from.

About this list

Every entry links out to the source. Descriptions and lessons are our own paraphrase — go read the originals.

PROGRAMOPERATORTOOLSTANDARD

Training

WHERE THE BUILD HABIT CAME FROM
PROGRAMai.joinleland.com

Leland AI Builder Program

A live, cohort-based program where knowledge workers build real agents and workflows across five levels.

WHAT WE TOOK FROM IT
  • Build on real work, never on toy examples.
  • Every session should end with something that runs.
  • A build log turns each fix into a compounding improvement.
Read the source
PROGRAMdolcoach.com

DOL Coach and Scott Kinder

Green Beret-founded project management training built on the idea that most teams have an execution problem, not a knowledge problem. What we took: plain-spoken PM that translates military planning — after-action reviews, risk routing, priorities — into business delivery. His free PM resources library is one of the best we've found.

WHAT WE TOOK FROM IT
  • Most teams know what to do; the gap is disciplined execution.
  • After-action reviews and risk routing are business tools, not military ones.
Read the source

Operators

PEOPLE ALREADY RUNNING THIS PLAY
OPERATORlinkedin.com

Jess Lynch — "10 Ways I Use Claude Code as My Chief of Staff"

A venture investor's multi-agent chief of staff system working across CRM, email, calendar, and notes.

WHAT WE TOOK FROM IT
  • When an agent gets it wrong, fix its instructions instead of redoing the work.
  • Save what works as reusable skills rather than one-off prompts.
  • Connect every tool you would otherwise check by hand.
Read the source
OPERATORpmairevolution.com

Antonio Nieto-Rodriguez and Ricardo Vargas

Former PMI chairs writing on how AI changes the practice of project leadership.

WHAT WE TOOK FROM IT
  • AI should strip out admin so leaders can actually lead.
  • Judgment and stakeholder relationships stay human.
Read the source
OPERATORsteveblank.com

Steve Blank

Stanford adjunct professor and co-creator of the Lean Startup and Hacking for Defense. What we took: get out of the building and prove it with customers. His 2026 argument that AI killed the MVP — that a day-one AI-built product is only an “Initial Untested Product” (IUP) until real customers prove it — shapes how we test every agent we build.

WHAT WE TOOK FROM IT
  • Customer contact beats internal conviction every time.
  • An AI-built product is untested until real customers prove it works.
Read the source
OPERATORsitreps.com

Sitreps

A veteran-built career transition community and recruiting firm covering MBA, consulting, finance, and defense tech paths. What we took: give real tools away free, build community in person, and translate military experience into civilian language without apology.

WHAT WE TOOK FROM IT
  • Give real tools away free and let the work speak.
  • Translate the military experience into civilian language without apology.
Read the source

Tools and standards

WHAT THE MARKET IS BUILDING TOWARD
TOOLcoworked.ai

Coworked

Makers of Harmony, an AI project manager for enterprise PMOs that works inside the systems a team already uses. What we took: AI should live where the work happens, and project leaders should lead rather than chase status. Harmony is the enterprise version of the idea; Pineland OS is the small-team version.

WHAT WE TOOK FROM IT
  • Go headless: work where the team already works.
  • Measure capacity returned, not features shipped.
Read the source
TOOLasana.com

Asana Dash and AI Teammates

A work platform positioning an AI chief of staff that routes work out to specialist agents.

WHAT WE TOOK FROM IT
  • Validation that one front-door agent routing to specialists is the right shape.
Read the source
TOOLplatform.claude.com

Claude Cookbook: The Chief of Staff Agent

Anthropic's reference build of a chief of staff agent using persistent instructions and subagents.

WHAT WE TOOK FROM IT
  • Persistent context files and specialist subagents beat one giant prompt.
Read the source
STANDARDpmi.org

PMI Standard for AI in Portfolio, Program and Project Management

The first formal standard for using AI responsibly in project work.

WHAT WE TOOK FROM IT
  • Govern AI use with clear ownership and verification.
  • Write the rules before the usage gets heavy.
Read the source

Continue the conversation

Reading something we should know about? Tell us.