It can only propose
Nothing changes on the board until a person clicks Approve. Not a setting, not a preference somebody can switch off in a hurry. The tool has no way to move your work on its own.
Journey started · audience of one: Braze's hiring team
When creative moves fast,
When creative moves fast,
someone owns how it moves.1
Your posting describes a job I already do. At Dow Jones I own how work moves through a brand team: intake, briefing, capacity, prioritization, and delivery, across event properties, campaigns, and fixed go-live dates, in Asana, which I own. Before that I was a Director of Creative Operations who built the function from zero. And when the process needed a tool that did not exist, I built it with AI.
This page is orchestrated like the thing you sell: one journey, one recipient, every claim a message with a source.
Press ⌘K anywhere to jump. An ops page should have an ops shortcut.
The week, as notifications
-
Relaynow
6 workbooks in. 1 resourced plan out. 1 field missing, follow-up drafted.
-
Asana2m ago
Q3 plan pushed. 0 fields re-typed. 120+ requests scoped since June.
-
Vizor9m ago
Week 41 is over capacity. A proposal is staged. Nothing moves until you approve.
-
Calendar1h ago
Fixed-date go-live: hit. About 8 events and 5 launches in 5 months.
-
Reference · Googleon record
"...targets across all workstreams without burnout."
Representative notifications. Every number in them is real, from the résumé, and resolved in footnote 7.
Clients and properties include Google, android.com, Google Search Ads, GE Healthcare, Dow Jones, WSJ, Barron's, MarketWatch, Microsoft, SAP Ariba, Vodafone, Merck, NYU Langone, Petfinder and ConEdison.
13+ years
Creative operations, program management, production. The title kept changing. The job did not.
120+ requests
Scoped and planned through Relay since June, from six teams' incompatible spreadsheets.
13 go-lives
About 8 events and 5 launches in the past five months, each on a fixed date.
Propose, then confirm
How I build AI into an ops workflow. A person approves before anything moves.
Step 01 · Message
Propose, then confirm
Your posting asks for AI-assisted workflows where they meaningfully improve speed, quality, or visibility. The word doing the work in that sentence is meaningfully, and I have a tested opinion about where that line sits, because I have built on both sides of it.
The same hour keeps going wrong in every creative team I have run. The resourcing meeting happens, real decisions get made out loud, and then somebody has to remember them and write them up afterwards. Usually late, usually thinner than what was said. The board drifts quietly out of date until the next meeting rediscovers it.
I built Vizor for myself, to manage my own team's capacity. The point of it is one sentence: the meeting should update the board, instead of somebody updating the board about the meeting. Building it forced four decisions I would not have thought about from the outside, and those decisions are the point of view I would bring to Braze.
Every card quotes the sentence that caused it
A suggestion with no source is one you either swallow or ignore, and both are bad. Carrying the exact sentence back means a proposal is something you can argue with rather than something you have to trust.
The audio never leaves the room
The speech becomes text on the laptop, and only the text goes anywhere. You are asking a team to let software sit in on the hour where workload and staffing get discussed. That is the most sensitive hour in their week.
It runs on the team's own AI account
Encrypted, revocable, and they see their own bill. Without a key the AI features simply switch off and the capacity planning still works. Nobody is locked in by the clever part.
None of the four is really a decision about AI. Each one is a decision about the meeting. Resourcing is the most politically loaded hour in a creative team's week: capacity, priority and whose work gets cut, decided out loud in front of the people it lands on. Automate a move out of that room and the person whose week just changed finds out afterwards. And the same judgment runs the other way: my rule for tooling is buy when a product does the real job, adapt when the gap is process rather than software, and build only when the near miss would force the team to reshape how it works. Most of the time, the answer is buy.2
Step 02 · Action
Six teams, six formats, one plan
Every quarter, six teams at Dow Jones send in their plans and requests. Subscription strategy, product design, product management, performance marketing, CRM, event marketing. Each sends its own spreadsheet, in its own shape, half of it written in a hurry.
Asking everyone for a single template has never worked anywhere I have tried it, so I built Relay to take the files exactly as they arrive. The teams never open it.2 Your posting calls this "intake through launch." Here is what my version of intake looks like when the front door has to read everything.
Click through the steps. The pipeline has six. This page shows the first and the last two, and keeps the middle three off the internet on purpose.12
Six workbooks, no shared template
Nobody is doing anything wrong. Six teams have six ways of describing work, because they do six different jobs. The fix is not a nicer form. It is a thing that reads all six, exactly as they arrive.
Six teams, thousands of cells, one plan out. The volume is why this is a system and not an afternoon.
The middle is the craft. The craft comes to the interview.
Between collecting and ranking, Relay does the three hardest things it does: it reads intent out of hurried prose, settles six vocabularies into one, refuses to guess a field nobody filled in, and chases its own gaps until they close. That much I will say, because the résumé already does.
How it does those things reliably is the part I am not publishing. Not because it is magic, but because it took real design decisions to get right, and those decisions are worth more in a room than on a page. This is also your answer to a question the posting implies: yes, I know the difference between showing the work and giving it away.
Ask me about the missing three steps. It is my favorite part of the interview.
It proposes the ranking. I own it.
Every item comes out of the middle carrying a reason and a capacity cost, so the order is arguable rather than handed down. Anything low confidence or over capacity does not get quietly sorted. It lands in a tray that needs a person.
- NowQ3 paywall testdesign 3d · copy 1d
- NextBarron's event micrositedesign 5d · eng 8d
- Needs meMarketWatch refreshover capacity
Where the human stays. Relay does the reading and the arithmetic. Priority is a judgment call and stays one.
Nothing gets re-typed
Planning finishes in Relay. Only then does the finished plan move into Asana, where execution runs and everyone sees their tasks. I own that Asana setup too, which is why the fields line up on both sides. Your posting asks for exactly this seam: workflows, templates and reporting that hold together because one person is accountable for the whole path.
Relay
plan, capacity, sequence
Asana
tasks, owners, status
Plan in Relay. Execute in Asana. Never distort the plan to fit the tracker.
Step 03 · Catalog
Three tools, one method
Same three questions for each one, because the transferable thing is the method rather than the subject. The middle question is the one nobody can answer without having built the thing. I build these to make my own programs run, not to leave creative operations.3
1 / 3
Step 04 · Decision split
The posting, audited
Twenty lines from the job description, grouped the way your posting groups them, and split the way a journey splits: met, or partial. Tap any line to open the proof. Every partial names exactly where the gap is, which is the reason to read them first.
Filter
Recruiters filter to Partial first. That is the point of having them.
Brand operations strategy and ownership
Own and evolve the end-to-end creative operations model, from intake through launchMet
That is my current job. At Dow Jones I run intake, briefing, prioritization, capacity and delivery for the Brand team: about 8 events and 5 launches in the past five months, each a fixed-date go-live, across 10+ event and conference properties. At Everyrealm I was Director of Creative Operations and built the model from zero, then hired the team that worked inside it.
Serve as the senior point of accountability for how work flows across creative, production, and executionMet
Five partner departments plan their design, content design and UX copy work through me. When six teams' quarterly plans arrive, they land on my desk, and one resourced plan leaves it. Steps 01 and 02 of this page are what that accountability looks like when it is built rather than described.
Drive cross-Marketing alignment on operating models, expectations, and ways of workingMet
The six teams that plan through my intake are marketing functions: subscription strategy, performance marketing, CRM, event marketing, plus product design and product management. The operating model is written down and running, not a deck. Getting eight property owners onto one shared build, step 05, is the alignment story with the most at stake.
Act as a strategic partner to Marketing, PMM, Events, Growth, and Regional teamsPartial
Marketing, events and growth-side functions, yes, weekly and by name. Regional is the honest gap: I have run localization across time zones on android.com, and I have not partnered with regional marketing teams across an office footprint like yours. That scale is part of why I am applying.4
Planning, capacity and delivery enablement
Partner with creative leadership to forecast workload, capacity, and resourcing needsMet
Capacity is computed, not assumed: PTO, standing meetings and partial weeks come off the top before anything is promised. I own the Asana capacity setup at Dow Jones, and I built Vizor because the meeting where those forecasts happen deserved a better instrument. A Google director is on record: targets met across all workstreams without burnout.
Balance internal teams, freelance support, and agency partners to enable scale and specializationMet
At Everyrealm I sourced and staffed the blend myself: 3D artists, UI and UX, motion and visual designers, internal and freelance, plus outside vendors like Monaverse, onboarded and held through implementation and platform testing to one coordinated launch. At Dow Jones I coordinate freelance support alongside the designers I plan for. And I spent years as the agency on the other side of that relationship, so I know what a good client looks like from both chairs.
Set clear expectations around scope, timelines, and delivery, and hold teams accountableMet
An executive director is on record with the phrase "expectation management both internally and externally," about a complex, large-scale project. The mechanism is unglamorous: written scope, a visible plan, and a review cadence that surfaces misalignment before build rather than during it.
Proactively identify risks, dependencies, and tradeoffs, guiding teams toward resolutionMet
Android 12 shipped against a public date that could not move, with creative, content, deployment and localization on the line. On Arizona Public Service, I structured the review cadence so 28+ engineers and skeptical utility executives found the misalignments early. Vizor's review clock exists because I watched projects slip on stakeholder feedback and wanted the slip visible before it became a miss.
Navigate ambiguity and competing priorities with confidence, diplomacy, and decisivenessMet
A year-long, deliberately ambiguous exploration of the future of Google Search Ads, run as a peer partnership with Google's Search UX Design Director. An MVP redesign shipped for a pharmaceutical client during the Endo and Mallinckrodt merger, where waiting for consensus was not on the menu.
Systems, process and tooling
Own and optimize Asana workflows, templates, SLAs, and reporting across BrandMet
The line in the posting I can prove fastest. I own my team's Asana implementation for reporting, capacity and resource management, and I built Relay to push typed, field-mapped payloads into it so nothing is re-typed. One honest clause: my reviews today run against per-reviewer baselines rather than published SLAs. Formalizing SLAs across Brand is work I would relish, not work I have already done.
Build scalable operational playbooks for campaigns, events, video, and always-on productionPartial
Events and campaigns, proven: the event portfolio at Dow Jones runs on a system that cut build time about 80%, six of eight properties migrated, and the go-live playbook has now run about eight times in five months. Video and motion are real but thinner: some video production at Dow Jones, and motion and 3D capability staffed and managed at Everyrealm rather than produced by my own hands. The playbook muscle transfers. The video depth is the honest partial.5
Identify and implement tools, automation, and AI-assisted workflows where they meaningfully improve speed, quality, or visibilityMet
Steps 01 and 02 are the point of view and the working example. The rule: buy when a product does the real job, adapt when the gap is process, build only when the near miss would deform how the team works. Behind it, about ten scheduled agents run on an Airtable system of record, behind human approval gates, with cost tracked per agent, so "is this automation worth keeping" has an answer instead of an opinion.
Ensure operational systems support both creative excellence and team sustainabilityMet
Your posting calls it work-life harmony. My reference calls it "targets across all workstreams without burnout," and she was the director watching. The system does the caring: honest capacity math, review waits measured instead of felt, and a plan that declines work out loud rather than absorbing it quietly.
Financial and vendor stewardship
Oversee creative budgets, vendor spend, and forecasting in partnership with FinancePartial
At Everyrealm I owned the function's spend: the freelancers, the vendors, the team I staffed. At Huge I tracked burn and spend across multiple Google properties and ran engagements that were among the agency's most profitable during my time there. What I have not done is own an in-house brand team's annual budget through a formal Finance planning cycle at public-company scale. Real gap, stated plainly.6
Lead agency onboarding, scoping, and procurement needsPartial
I have onboarded and scoped external partners from the client side, at Everyrealm through implementation and platform testing to a coordinated launch, and I spent years being the agency on the other side of the table at Vertic, Huge and POSSIBLE. That means I can tell a real vendor efficiency claim from a markup, and write a scope that does not get gamed. A formal procurement process with a sourcing team is the part I would be doing for the first time.6
Partner with People, Finance, and Marketing leadership on org health, resourcing strategy, and long-term scalePartial
Resourcing strategy and org health through the capacity lens, yes: that is most of what this page argues. Standing partnership with a People team on headcount planning and org design is the part I have done informally, at a startup where I was the one doing the hiring, rather than formally, inside a People org's own cadence.
Who you are
8 to 10+ years in creative project management, creative operations, or production managementMet
Thirteen-plus, across all three of those titles, including a year as Director of Creative Operations. The title kept changing. The job did not.
Proven experience leading operations for in-house creative or brand teamsMet
Twice, in the two hardest configurations: built from zero at Everyrealm, where nothing existed until I made it, and inherited at Dow Jones, where the work was already moving and the system had to be improved underneath it without dropping anything.
Influences without direct authority through trust, clarity, and consistencyMet
Two years inside Google's Android pod from Huge, leading four to six designers whose reporting lines all ran elsewhere, holding a peer relationship with Google's Search UX Design Director. Four references on record, from a Design Ops practitioner, a director, an IC designer and an executive director. Four altitudes, on purpose.
Thinks in systems, not tasks; designs processes that scaleMet
Step 03 is what that looks like when it stops being a phrase. I do not just design processes that scale. When the process needed software that did not exist, I built the software, and built it to propose rather than to act, because that is what a system designed by an operator looks like.
Step 05 · Experiment, with results
Eight property builds, one system,
Eight property builds, one system,
and the part that was not engineering
This number is usually reported as an outcome: eight website properties unified into one, six of eight migrated, build time cut about 80%. Reported that way it sounds like an engineering result.
It was not. One engineering team did the building. The system half was design work: tokens defined in Figma for every brand asset across the event brands, so eight properties could run on one system and still each look like themselves.
My part was the agreement and the expectations. Consolidating eight property-specific builds meant getting the people who owned them onto a faster shared one, then holding them steady through migration, which is the half that has nothing to do with engineering.7
Two of the eight are not migrated yet. Six of eight is the honest state of it, and it is the number I would rather report than a rounded one.
I put this here because it is the fair challenge to step 03. Relay has one user and Vizor is a private beta, so if you want evidence that I can get other people to change how they work rather than build something they might, this is the piece of the record that carries it.
Six of the eight properties are migrated. Two are not.
Step 06 · Event history
The title kept changing. The job did not.
Thirteen-plus years of the same work under names that kept changing, because the function did not have a settled one. Your posting settles it.
Huge @ Google · 2020 to 2022
android.com, through the Android 12 launch
Roadmap, creative, content, deployment and localization across android.com, tv.google and wearos.google.com, against a public date that could not move. I tracked burn and spend across the properties, and the engagements were among the agency's most profitable during my time on them. Separately, a year-long research and design phase for the future of Google Search Ads, leading four to six designers with Google's Search UX Design Director and his team.
Everyrealm · 2022 to 2023
Creative operations, built from nothing
Director of Creative Operations at a Web3 metaverse start-up that initially received $50M+ from a16z and others. I sourced and staffed the team of 3D artists, UI and UX, motion and visual designers, balanced internal hires against freelance support, owned the function's vendor and freelance spend, and introduced the intake, review rituals and capacity visibility as one system. The function did not exist before I arrived.
Vertic · 2017 to 2020
A design system that had to survive 28+ engineers
A new transactional .com and mobile app for Arizona Public Service, built on a comprehensive design system, after a three-month research phase and an eight-month design phase, delivered with Infosys and 28+ engineers. I structured the review cadence so misalignment surfaced before build rather than during it.
GE Healthcare · freelance
Evergreen production, at volume
The asset-production phase of the global Better Health Study, one of the company's largest marketing campaigns: executive-level visualizations, a global website, and hundreds of media assets delivered through one gated publishing pipeline. Keeping leadership aligned on a cadence while the volume flows underneath is the same job as making a brand function legible.
The Row · an Everyrealm project
Holding outside work to a standard
A members-only metaverse of one-of-a-kind 3D architectural landmarks by renowned artists. I owned the external vendor relationship with Monaverse through implementation and platform testing to a single coordinated launch, plus external motion, 3D rendering and video production. Vendor stewardship is half of your fourth pillar, and it is where I have real mileage.
1 / 5
- 2013 to 2015Beyond, Digital ProducerGoogle's "Google for Work" site, on a tight deadline, with a team across time zones.
- 2015 to 2016POSSIBLE, Digital Project ManagerPetfinder.com redesign, rebrand and launch campaign. Purina Veterinary. ConEdison's new .com.
- 2017 to 2020Vertic, Senior Digital Project ManagerVodafone, SAP Ariba, Microsoft, Merck, and the Arizona Public Service program.
- 2023 to presentFreelance, Sr. PM and Digital ProductionGE Healthcare. Moving Brands, a UX and IA audit for NYU Langone's design system. Prophet, an MVP redesign during the Endo and Mallinckrodt merger.
- 2026 to presentDow Jones, UX Program Manager, BrandBrand steward for product touchpoints across WSJ.com, Barron's.com and MarketWatch.com. The eight-into-one design system. The Asana implementation. About eight events and five launches over five months. Built Relay.7
Step 07 · Messages received
Quoted, not paraphrased
Five references in full. A Design Ops practitioner, a director, an IC designer, an executive director, and a design lead who uses a tool I built. Five altitudes, on purpose.
Diligent on the financial, creative and timing dimensions, a go-getter, with strong UX and design input.
Owned creative, content, deployment and localization on android.com, with meticulous capacity planning to hit targets across all workstreams without burnout. Exceptional communication and problem solving.
It turned our weekly planning meeting from a doc-readout into a real conversation, and now the conversation updates the board itself.
A year-long program at Arizona Public Service, complex and multi-part, with both project and client management. A team player and problem solver who built strong client relationships.
Exemplary program management on a complex, large-scale project. Diligent planning, adaptability, and expectation management both internally and externally. His role was critical to its success.
1 / 5
Step 08 · Scheduled sends
The first 90 days, as a journey
Braze customers would call this a drip campaign. Each step waits, fires, and names the thing that exists at the end of it. A plan whose output is "alignment" is not a plan.
- Weeks 1 to 2
Read the queue, not the org chart
Every path work takes into Brand: where it enters, who bypasses the front door, and why they are right to. Sit with the Creative Directors and ACDs first, because the ops model exists to serve their bar, not the other way around.
Output: a map of how work actually arrives, including the routes nobody documented.
- Weeks 2 to 4
Audit Asana against the lived workflow
The posting says own and optimize, which implies a gap between the documented process and the real one. Find it: templates, fields, statuses, the reports leadership actually opens, and the ones nobody does.
Output: a gap list ranked by pain, and the two reports worth keeping.
- Weeks 4 to 6
Baseline capacity, the calendar, and the spend
Real capacity after meetings and PTO, a ritual audit, and an inventory of vendor and freelance spend before renewal season decides for us. Three inventories of what the org has already said yes to.
Output: an honest capacity picture, a kill-or-merge list, and a spend map for Finance.
- Weeks 6 to 8
Publish the prioritization logic, and set SLAs with the leads
Written, observable principles, so priority becomes a lookup rather than a negotiation and the loudest requester stops winning by default. SLAs agreed with creative leadership, not imposed on it.
Output: one page, in the open, that anyone can check my decisions against.
- Weeks 8 to 10
One AI pilot, small and real
Two genuinely painful recurring parts of the week, rebuilt with the people who own them, with a measured before and after. Not an org-wide rollout nobody asked for.
Output: a working thing two people use every week, and a number.
- Weeks 10 to 12
Make the function legible, and give a piece of it away
One leadership view, one short changelog, one adoption number per surface. Each owned by someone other than me.
Output: a reporting cadence that survives my calendar, plus the first written case for where Brand ops should invest next.
A note about the calendar
Forge lands inside this plan, and the plan knows it
Forge 2026 runs September 28 to 30 in Las Vegas. Depending on start date, the biggest event of Braze's year falls inside these 90 days. Good. Event weeks are when an operating model shows its real shape, and I would rather learn the Brand team's pressure points during its Super Bowl than from a retro deck afterwards. The plan above bends around the work, not the other way.8
Not in the first 90 days
Reorganize anything, replace a tool, or introduce a framework with a name
All three look like leadership. All three spend the trust you need to make the boring changes that work.
Step 09 · Conversion event
Brazing joins metals that would not otherwise hold.
Brazing joins metals that would not otherwise hold.
Good name for the job.
Your company is named after a joining process: two different metals, held together by a filler that flows into the seam and sets stronger than either expected. Your posting describes this role as the connective layer between creative ambition and operational reality. Those are the same sentence. I have spent thirteen years being the filler metal, and it is the first posting I have read that names the job that precisely.9
Three specific things drew me, beyond the metaphor. First, the brand work is made in-house and made seriously: your executive creative director has written publicly about rebuilding the brand with an internal team, migrating thousands of pages in the process. A brand org that takes on that production volume in-house is exactly the kind that needs one person accountable for how the work moves, and the posting reads like it was written the morning after someone realized it.
Second, the culture copy matches my references rather than my adjectives. Braze writes "work-life harmony" into every posting. The strongest quote on this page is a Google director crediting meticulous capacity planning that hit targets across all workstreams without burnout. I did not ask her to phrase it that way. That is what work-life harmony looks like from the ops chair: not a perk, a planning discipline.
Third, Braze sells orchestration. The product's whole argument is that messages, channels and timing should run through one system that a human directs. This page is built the same way on purpose: one journey, segmented for its audience, every send sourced. I would be making that argument one floor up, about creative work, in a company that already believes it at the product level. I am happy at Dow Jones and doing well there. But I do my best work where the operating layer is understood to be the point, and a company that put "how work moves" in a job title is that place.
Every journey needs a CTA
You wrote the job description
You wrote the job description
for how I already work.
Producer, project manager, Director of Creative Operations, program manager. This posting is the first one that asks for all of it at once, including the part I built on nights and weekends. I would like to talk about it.
pr.wvelazquez@gmail.com · 917-554-5173 · New York · LinkedIn · PACTO
Fine print, promoted
Every marker on this page resolves here
A page that argues for operational rigor should qualify its own claims. These are not fine print. They are the part I would want read first.
- 1.The step up. I run creative operations for a brand team now, at Dow Jones, and I have built the function once from nothing, at Everyrealm, where I also hired the team. What I have not done is run creative operations for a global brand organization at Braze's footprint and public-company scale. That is the step up, and it is the reason I am applying rather than a thing this page hides. Back to the audit
- 2.The AI claims, which are the ones to read. Relay has exactly one user: me, every week, on real quarterly planning. The six teams send spreadsheets. They never open it. One person using a system weekly on real data is a better validation signal than a signup count, and it is also not adoption, and both of those are true. Vizor is in private beta, invite-only, used by me and a few agencies run by friends, and is not deployed across Dow Jones. PACTO is private, two or three users. So: I have built the tools and workflows the posting asks about, and I have not yet rolled an AI-assisted workflow program out to a marketing organization. Nearest evidence I can move other people: step 05. Back to step 05
- 3.Not an engineer. I write the requirements, direct the AI agents that build, then review and correct, with infrastructure feedback from staff engineer friends at Amazon and Google. I do not hand-write production code, and nothing here should be read as claiming I do. I am also not starting a business. The tools are proof of how I take an operational problem apart, not a venture with a future. This page itself was built the same way: I directed, reviewed, and corrected.
- 4.Regional. Braze's postings describe a global company with offices across four continents. My global experience is real but narrower: localization and time-zone delivery on android.com and multi-country campaigns agency-side. Partnering with regional marketing teams as standing stakeholders is a muscle I would be building at Braze, not bringing. Back to the audit
- 5.Video and motion. I have managed video production within event and campaign work at Dow Jones, and staffed and directed motion and 3D capability at Everyrealm and through external vendors on The Row. I have not run a dedicated video production pipeline end to end. Fluent in the workflow, not a producer of the craft. Back to the audit
- 6.Budgets and procurement, precisely. Owned: creative function spend at Everyrealm, covering freelancers, vendors and the team I staffed. Tracked and answered for: burn and spend across multiple Google properties at Huge, where my engagements were among the agency's most profitable during my time there. Profitability at an agency is creative ops with the invoice attached: utilization, scope discipline and burn, watched weekly. Not yet done: an in-house brand team's annual budget through a formal Finance cycle, or a procurement process run with a dedicated sourcing team. Both stay marked partial. Back to the audit
- 7.The Dow Jones figures. Every Dow Jones number on this page, including the ones in the hero notifications, comes from my résumé: eight properties with six migrated, build time cut about 80%, about eight events and five launches over five months, 120+ requests scoped and planned through Relay since June, six requesting teams, five partner departments. The notifications themselves are representative renderings of real events, not screenshots. Relay is internal with no public address.
- 8.Braze facts. Every Braze fact on this page comes from Braze's own published material as of August 2026: the job posting, braze.com, the brand refresh interview with your executive creative director, the Forge 2026 site, and press releases. Forge 2026 dates: September 28 to 30, Fontainebleau Las Vegas, per forge.braze.com. This page states no Braze metrics beyond what Braze has published, and no internal knowledge is claimed. If any of it is out of date, that is my search, not your team.
- 9.The metaphor. Braze's original brand identity was built on the metallurgy of brazing: joining metals by flowing a filler alloy into the seam. That reading of the name comes from the public case study by the studio that designed the identity. If the team has moved on from the metaphor, I am happy to move on with it. The job description still describes a connective layer, and I still am one.
- 10.The styling. Built with Braze's published design language, read from braze.com's shipped stylesheet: the purple, orange and pink, the radial gradients, the pill shapes, the light surfaces and the deep purple ones. No Braze logo, no Aribau Grotesk font files, no copied code. The type is Hanken Grotesk, a free substitute chosen for a similar grotesk voice. The journey conceit borrows the vocabulary of customer engagement, not any Braze interface. Every chart and diagram uses representative values and says so.
- 11.Not affiliated. This is an independent page by Warren Velázquez. Not affiliated with, endorsed by, or connected to Braze, Inc.
- 12.What is withheld, and why. Relay's pipeline has six steps. This page deliberately shows three. The middle ones, how it reads intent, normalizes six vocabularies, and runs its follow-up loop, are the result of design decisions I would rather discuss than distribute. What remains on this page is what my résumé already claims; what is withheld is how it actually works. An operations lead who publishes the runbook before the first conversation is not demonstrating openness, just poor scoping. Back to Relay