meet tricia
M.Phil. Clinical Psychology, Stony Brook University · Concentration: Quantitative Analysis
I see the wiring beneath complex systems.
I’ve worked in clinical research, behavioral science, publishing, consumer products, technology, recruitment, operations, and retail.
The same discipline applied across domains.
I find the structure beneath a complicated problem, separate signal from noise, and translate what I find into content, workflows, and decisions that hold up beyond the meeting. Sometimes that looks like scrutinizing and translating clinical evidence. Sometimes it means diagnosing a failing workflow, mapping business needs to technical requirements, or identifying where an answer sounds correct but misses the core question.
The throughline is judgment under complexity. Determining what is missing, and what happens when an answer meets the front line.
areas of expertise
PET NUTRITION & WELLNESS
public health
CONSUMER PRODUCTS
PROJECT/PROGRAM MANAGEMENT
BUSINESS REQUIREMENTS DEFINITION
Cardiac Electrophysiology & Rhythm Management
CMS/ATS IMPLEMENTATION
GRANT-FUNDED RESEARCH
BUSINESS OPERATIONS
CLINICAL PSYCHOLOGY
STRATEGIC CONTENT
oncology & palliative care
RETAIL OPS
Autoimmune & Inflammatory Disease
MARKETING & COMMUNICATION
PATIENT & CAREGIVER EXPERIENCE
Alzheimer’s disease
dysautonomia
I tend to look one layer underneath the obvious question.
Is the claim actually supported? What assumptions are hiding inside it? What changed upstream to produce this outcome? What would make the answer technically correct but practically useless?
My work is about making that underlying structure visible and then translating it clearly.
Accuracy matters. So do context, consequences, and whether an answer survives contact with reality.
Who i am
-
I start by asking what is actually happening — not simply what the source material says is happening.
What does the evidence support? What assumptions are being made? What information is missing? Who needs to use the answer? And what constraints will determine whether it works in practice?
From there, I separate evidence from assertion, identify the strongest available sources, test claims against context, and organize the information around the decision someone actually has to make.
I care about failure modes as much as getting successful answers. Something can be technically accurate and still be misleading, incomplete, badly framed, impossible to implement, or wrong for the person receiving it.
-
Complexity isn’t a problem to simplify away. It is a structure to make visible.
Clear communication should not require flattening complexity, hiding uncertainty, or steering someone toward a predetermined conclusion.
That means being precise without hiding behind jargon, accessible without distorting the underlying evidence, and explicit about assumptions, limitations, uncertainty, and trade-offs.
I am skeptical of confident answers that outrun their evidence. I value the willingness to say “we don’t know,” “that doesn’t follow,” or “that answer misses the real problem” when that is what the situation requires.
-
I’ve spent my career moving toward the layer underneath.
The visible task is rarely the whole task.
A research study is also a system of incentives, assumptions, definitions, and consequences. A piece of content is also a decision architecture. A workflow reveals what an organization actually values, regardless of what it says it values. A product recommendation can be technically defensible and still fail the person standing in front of you.
That is the pattern I keep returning to.
I am drawn to the places where disciplines overlap and where the official explanation stops being sufficient. I want to know what is shaping the outcome, what has been left out of the frame, which constraints are actually governing the situation, and where the leverage really sits.
Over time, that has made me less interested in titles than in underlying mechanisms.
Research taught me to interrogate evidence. Psychology taught me to pay attention to behavior, perception, and context. Writing taught me that framing changes what people can see. Technology and operations taught me that systems quietly determine what is possible. Frontline work taught me that elegant theories are only as good as what survives contact with real people.
The result is a way of working that crosses domains without becoming vague. I find the structure beneath the complicated problem and make it visible.
Seeing the walls is the easy part. What comes next separates people who understand the system from people who change it.
Ready to build something different? Let's connect.
