Home› The operating model
The operating modelRhythms, intake, capacity, rituals, tooling and visibility are what the function provides. Designers, researchers, content designers, leadership and the partner Ops teams are who it serves, and adoption is how you know it worked. The failure mode isn't a weak system but someone who couldn't find what they needed, didn't trust it would hold, or found it cheaper to work around you.
Everything a central function provides has someone it's for, a value proposition, and a reason someone decides it's cheaper to do it themselves. Naming that reason honestly is most of the job. Here's the whole set for a 130+ person Design and Research org.
The quarterly and monthly cadence that keeps 130+ people pointed the same way, without nine meetings to find out where.
One front door, and written principles for how the queue is ordered, so priority is a lookup instead of a negotiation.
An honest read on what the org can absorb, so commitments are arithmetic rather than optimism and "we're at capacity" is a number, not a mood.
Standups, crits, retros, reviews. The connective tissue of craft, and the easiest thing in any org to quietly ruin by adding to it.
Figma, Jira, Notion, Cursor, Claude, Google Workspace, plus whatever accumulated quietly. Chosen deliberately, adopted properly, and paid for on purpose.
Newsletters, dashboards, executive summaries. What stops a central function having to argue for its own existence every planning cycle.
The first ninety days are laid out step by step on the about page: people first, then the queue, then the calendar, then one small AI pilot. This is what comes after, once there's enough trust to change how the function operates.
Nothing enters prioritization until it's actionable. A backlog of vague intentions turns prioritization into a debate about interpretation instead of value. Granular enough to finish, in one place, with an owner.
Done it: at Dow Jones the definition of ready is enforced in Relay, where planning, structuring, prioritization and resourcing happen and automated follow-ups chase the half-baked briefs until they're ready. The structured output transfers through Asana's API into the execution and reporting layer I own, across ~8 events and 6 launches over the past five months. The full AI point of view →Consistency where it saves people effort, difference where the disciplines genuinely differ, and a bias toward adopting a neighbour's working practice over inventing a parallel one. Being a generous citizen of an Ops community mostly means giving away what you built.
Doing it: I'm the brand steward for product touchpoints and product-connected materials at Dow Jones, partnering daily with product design teams and fielding work from six functions. The seam is my current job.External work has to arrive at the standard and in a format the workflow can accept: front-load the spec and test far earlier than anyone wants to, rather than reviewing harder at the end.
Done it: owned the Monaverse relationship through implementation and platform testing to launch, plus external motion, 3D and video vendors. Also delivered from the agency side at Moving Brands and Prophet.Every program gets an owner who isn't me. Coaching is mostly handing over something slightly too big and staying close enough to catch it. Not stepping back: getting the hours for what only the function's lead can do, standards, staffing, vendor strategy and the calls that need judgment. A function should keep running while its lead is on holiday, and its lead should spend that reclaimed time on what comes next.
Done it: sourced, hired and trained the Everyrealm creative team, then handed them the process rather than the instructions.A design org's tool stack is a set of standing commitments that renew whether or not anyone is looking. Where I'd want a good partner is named below, because this is the part of the role I've done least formally.
The first artifact I'd build is unglamorous: every tool, its cost, its renewal date, its owner, and what fraction of the licenced seats are used. Most stacks have at least one line item that is entirely a habit.
It usually happens because a team needed something on a Tuesday. A legitimate reason, so the fix is to pick one deliberately and migrate the loser properly, not to send a note telling people to stop.
Procurement, Finance and Legal move fastest when you arrive with the alternatives priced, the adoption plan attached and the risk named. I've been on the agency side of these contracts, a useful education in how they're really scoped.
The most expensive tool in any org is the one that was bought, announced and never taught. Half the team keeps using the old thing and you're paying for both.
In the age of AI, software bends to the real business need, so for any workflow the market doesn't serve, "build it" is a legitimate answer, sometimes a days-long one, against a five- or six-figure annual line item that still wouldn't fit how the team works.
AI collapsed the cost of implementation, not the cost of thinking, so I build the traditional way: research the problem, define it, write requirements, then build. That guardrail stops "we could just build it" becoming a shadow stack nobody maintains. And because I build with Claude and Cursor rather than evaluating them from a distance, I can tell a tool a design team will absorb from one that demos well.
Vendor management ✓. Commercial exposure from the agency side ✓. Delivery inside legal constraints during the Endo–Mallinckrodt merger ✓. Profitability via resource utilization and capacity management is a stated strength ✓. But a full Procurement and Finance cycle for a design org's stack? Not yet. I'd want a strong partner through the first renewal season and would say so on day one rather than discover it in month four.
The complete map. Where the match is partial, it says partial. That's the point of a table.
Relay, the AI intake and planning layer he built for himself, turns 6 teams' inconsistent quarterly spreadsheets into one resourced plan. Then the Asana execution and capacity model carries ~8 events and 6 launches over the past five months.
Quick look: the detail
A Huge-side team of 4–6 designers led through a year-long exploration, embedded alongside Google's Search UX Design Director and his designers, plus one launch calendar across three web properties.
Quick look: the detail
Eleven months of research and design into production with Infosys and 28+ engineers, and a review cadence that kept skeptical executives inside the process.
Quick look: the detail
Owned Monaverse through implementation and platform testing to one launch, plus external motion, 3D-rendering and video vendors.
Quick look: the detail
Executive-level visualizations that kept a global campaign aligned on a cadence, with gated review holding quality across hundreds of assets.
Show me how work reaches Design and Research today and I'll tell you where the leaks are. That's the conversation I'd most like to have, and the fastest way to find out whether I'd be useful.
pr.wvelazquez@gmail.com · LinkedIn · warren.digital · New York, commutable to Brooklyn