03 · frameworks and tools

Frameworks and tools

These frameworks and tools support decisions about delivery, people and client accounts. I designed them around recurring problems, with shared criteria and records that managers and teams can use in their work.

02 · The method

Frameworks

The frameworks I built and the idea behind them.

  • DPET and SPET

    Quarterly and per-sprint reviews that give managers shared criteria for performance, staffing and promotion decisions. From the case: A common basis for performance and staffing decisions
  • Staff augmentation retention program

    Regular one-on-ones and protected training time for engineers placed with clients. From the case: Leading the move to staff augmentation

    The problem was visibility. We were the last to know when a placement had trouble, and the first sign was usually a client email, after time had already been lost.

    The program has two parts. Regular one-on-one and coaching meetings with each placed engineer show where that person stands and catch risk before the client sees it. Training and protected time then help people close the gaps those meetings find.

    We now hear about a struggling placement from our own engineer, before the client has to write. We then drive the conversation with the client ourselves, before it becomes a problem.

    Leading the move to staff augmentation →

  • Organizational space

    Using the history of past project decisions as context for new ones. From the case: AHM, account health in one place

    My master’s thesis proposed using the history of past project decisions as context for new ones. I call the setting an organizational space: the policies, practices and people shared across an organization’s projects. Experience stays with the organization when it is recorded there, and leaves when people leave.

    Several things I built since apply the idea: the knowledge base in YouTrack, the history AHM keeps for each client and the recent-sprint record in SPET.

    AHM, account health in one place →

03 · The means

Tools

The tools I built and the stack I work in.

  • AHM

    A shared record of account history, feedback and risks for earlier decisions. From the case: AHM, account health in one place

    SvelteKit and PostgreSQL, in production with about 15 accounts. See the case.

    AHM, account health in one place →

  • TCF platform

    The platform behind the Cognitive Leader Framework, which is our CEO's work. From the case: AI in delivery: a lab, a workflow and three projects

    I authored and maintain it in Next.js and MongoDB. How it came about is in the case on AI in delivery.

    AI in delivery: a lab, a workflow and three projects →

  • My own tools

    Tools I build for my own use with agentic workflows.

    I also build tools for my own use with agentic workflows, each started to solve a problem I had. More on the life page.

  • tmwhy-agents

    A command-line tool in Go that reports how agentic workflows are set up across projects.

    A command-line tool written in Go. It scans a root folder and reports the current agentic setup in each project it finds, so I can see at a glance what is configured where.

  • Technical scope

    The agentic tools, stacks, data and hosting I work with.
    • Agentic tools: Claude, GitHub Copilot and Codex.
    • Stacks: Next.js, React, Node.js, SvelteKit, Django, Python and Go.
    • Data and hosting: PostgreSQL, MongoDB, DigitalOcean, Vercel and Supabase.