1
Ambiguous Brief
A loose intent, often no data, no benchmarks, no assets.
How I work · The Structure-First Operating Model
When a problem is ambiguous, I create structure.
Across every engagement, a marketing agency, a hardware launch, a luxury e-commerce site, a B2B safety product, the same sequence shows up. I call it the Structure-First Operating Model: diagnose the real problem, then build a system a team can repeat.
AmbiguityDiagnosisRoot causeStructureExecutionMeasurementRepeatable system
01 · How I work
The Structure-First Method.
One decision sequence repeats across every engagement, regardless of industry: diagnose before executing, find the real problem, impose structure, and leave behind a system others can run.
From an ambiguous brief to a system that outlives the engagement
Eight steps, applied the same way in eight industries
2
Diagnose
SWOT, audit, or competitor teardown before any execution.
3
Isolate the Root Cause
Name the real problem, not the stated one.
4
Impose Structure
Turn intent into a concrete artifact: architecture, brief, framework.
5
Build a Repeatable System
Template it so it survives past this one project.
6
Coordinate Execution
Brief and direct specialists toward one shared outcome.
7
Measure & Reuse
Anchor to the one metric that matters; the system compounds.
What repeats is not a specialty. It is a sequence. Nearly every engagement opens the same way: a SWOT, an audit, or a competitor teardown, produced before any deliverable. The vague then becomes concrete: “we need a website” turns into a landing-page architecture; “optimize the listing” into briefs precise enough for three specialists to execute.
And the structure is built to be reused: templates redeployed across clients, discovery questionnaires standardized, one scoring rubric applied identically to seven competitors. The instinct is to leave behind a system, not just a set of outputs.
“When a business problem is ambiguous, I create structure, identify the real issue, and build a repeatable system to solve it.”
The pattern the evidence keeps pointing back to
02 · The decision sequence
The model, step by step.
A closer look at how the operating model moves from an unclear ask to a measurable, reusable system.
1
Start with the ambiguity, not the ask
The stated request ("more marketing," "improve this page," "redesign the site") is rarely the real problem. I treat the vague brief as the starting point, not the spec.
In practice: N-iX, "improve this page" became a growth diagnosis2
Diagnose before prescribing
I audit the business first, the offer, the audience, the funnel, the analytics, and write down what's actually broken before proposing a single deliverable.
In practice: Real Authentication, the audit found the growth gap3
Trace it to root cause
Symptoms ("low conversion") get traced to the underlying cause (an unclear audience, an undecodable message, no defined position) so the fix addresses the disease, not the symptom.
In practice: Velocity Vue, weak conversion traced to an illegible message4
Prioritize the highest-leverage move
With limited budget and time, I sequence: deciding what to do first, what to defer, and which single decision unlocks the most (a category focus, a repositioning, a segmentation model).
In practice: ServaxNet, segmenting a technical product into packaged solutions5
Design the operational structure
I turn the decision into machinery: a template, a framework, a pipeline, a calendar, with named owners, hour budgets, and states so the work is legible and doesn't live in one person's head.
In practice: Greaux Digital, one delivery pipeline for 21+ accounts In practice: Texas Remodeling Pros, a quarterly organic system revealed the next growth category6
Lead cross-functional execution
I coordinate specialists, design, copy, web, SEO, paid, through a weekly cadence, routing work and unblocking dependencies so multiple workstreams ship as one system.
In practice: Mob Armor, a five-person pod, four launches7
Measure against the real goal
I instrument outcomes, goals, micro-conversions, ROI reporting, and read the honest signal, including the metric that goes the wrong way, to steer the next cycle.
In practice: Mob Armor, client ROI reporting drove the next quarter8
Leave a repeatable system
The deliverable is never the point; the system is. The best result is a machine that keeps running, reused across quarters, handed to a team, or still live years later.
In practice: Real Authentication, the template still runs the client's directory todayThe value is not any single deliverable. It is the reasoning system behind it.
The same operating pattern lets me move between industries without relying on surface-level expertise: establish the evidence, clarify the decision, create the structure, and make execution legible to everyone involved.
Better decisions
Assumptions are made explicit before they quietly shape the solution.
Cleaner execution
Owners, priorities, dependencies, and measures are defined before work begins.
Reusable value
The framework remains useful after the first project, launch, or engagement ends.
03 · Toolkit & credentials
Full stack, by category.
Project & program management
Asana · Jira · Monday.com · Smartsheet · ClickUp · Notion · Airtable · Confluence · Miro · Lucidchart
Marketing, CRM & automation
HubSpot CRM · Salesforce (basic) · Meta Business Suite · Hootsuite · Sprout Social · MailChimp · ConvertKit · Zapier
Analytics & SEO
Google Analytics · Looker Studio · SEMrush · Ahrefs · Google Search Console · Hotjar · SpyFu · Yoast
Creative, content & AI
WordPress · Canva · Adobe Lightroom · Loom · Claude · ChatGPT · Gemini · AI content workflows
Education
B.S.B.A., Magna Cum Laude, UTSA Alvarez College of Business
PMP Certification, PMI, actively studying
Key certifications
HubSpot Solutions Partner · Google Analytics IQ · Google Ads Search · Digital Marketer (Content, Social, Copywriting, Community) · LinkedIn Learning: Program Management Foundations, Program Strategy, Agile Foundations
04 · Proof of thought process
N-iX: from “improve this page” to a defensible growth diagnosis.
The original interview presentation, exactly as delivered: an ambiguous brief turned into prioritized recommendations in one hour.
Duration1 hour
RoleGrowth PM interview candidate
DeliverableUX evaluation + growth recommendations
ScopeLanding-page optimization
Context: a time-boxed 2022 interview exercise, built from a public landing page and a high-level brief, with no analytics or internal research. It demonstrates the approach, not a production redesign.
Let's talk