Menu

Jamie Taylor

  • Program Lead
  • content-rich experiences and delivery systems

Studio profile

Jamie Taylor — Program Lead

Jamie Taylor is a Program Lead, overseeing engagements where several pieces of work have to succeed together. Jamie's focus is content-rich experiences and delivery systems, which suits clients whose websites carry large libraries of articles, products, guides or resources that many people contribute to.

As Genome's relationships with clients deepen, single projects often grow into longer programs combining strategy, design, engineering and Shopify Plus work. Someone needs to look across the whole arc and keep it coherent. The program lead role exists for that long view, connecting this month's work with what the client hopes to have built a year or two from now.

In client conversations Jamie often asks about the people behind the content: how many contributors there are, how they learn the tools and what slows them down. Delivery systems, in Jamie's sense, include those human workflows as much as software and schedules, because a content-rich experience is only as good as the team keeping it current.

Large content estates turn accessibility into a question of scale. One flawed template can repeat a barrier across thousands of pages, while one well-made template can remove it everywhere at once. Jamie prioritizes that kind of structural fix, and argues for retiring content that no longer serves anyone, which keeps sites lighter and easier to look after.

Jamie regularly works with client editorial teams, translation partners and other agencies active on the same estate. Clients should come away with a program they can see as a whole, a sense of steady progress on many fronts, and systems that let their own people keep publishing well.

Learn about the wider team, explore the studio services, or visit the contact page to start a conversation about your own product challenge and see how program coordination could help.

Running several workstreams without losing the thread

Some engagements are bigger than a single project. A brand refresh, a new content platform, a commerce migration and a run of campaign pages might all be in motion together, sharing people, content and deadlines. A program lead keeps those streams pointing the same way and makes the links between them visible.

Jamie’s main tool is a dependency map showing which stream waits on which. The commerce templates need the content model. The campaign pages need the new design system. The migration needs clean product data before anything else can move. Next to it sits one shared release calendar, so nobody discovers late on that two teams planned to launch on the same Tuesday. Content-heavy programs add another layer: migration plans for large volumes of pages, redirects mapped URL by URL, and editorial sign-off scheduled like any other piece of work.

What Jamie guards against is local optimization, where each stream hits its own targets and the program as a whole still misses. A biweekly program review gathers stream leads around shared milestones rather than separate task lists. Delivery directors run their own streams; Jamie coordinates between them and brings cross-stream decisions to the client partner early, before they harden into conflicts.

On the program board at all times

  • Every workstream, its lead and its next milestone
  • Cross-stream dependencies, each with a resolve-by date
  • A shared calendar for releases and content migration
  • Decisions waiting on the client, oldest first
Team

A practice built for thoughtful progress

The profile above is intentionally fictional and represents a program coordination role within a collaborative studio. Explore the services, browse the work, or read the journal to see how this perspective supports useful digital products.