We turned a trusted practice and growing community into a bilingual experience, product system, and more disciplined way of continuing the work.
Nari came to me with a trusted voice, a growing audience, years of teaching, and more useful material than any platform could hold.
I reframed her growth challenge as a systems problem: how could her expertise become a coherent practice that people could use, Nari could sustain, and the business could grow around? The value was already there. It needed an architecture.
Formation arc
Voice→Brand→Platform→Support→Product→Operations
Nari already had a clear voice. My job was to create the structure needed to turn it into a scalable business.
The short version
If you only read four things
Situation
Trust without structure
Real expertise and a real audience, delivered post by post and dependent on Nari being present.
The read
Parents arrive in crisis, not curiosity
One finding reframed the engagement from a content problem into a support problem.
What I built
A practice system, not a website
Four quick guides, a bilingual platform, a governed brand system, and the operating model behind them.
Where it stands
Attention validated Distribution not yet
Parents stay with the support and move deeper into it. Reach, adoption, and revenue remain unproven.
01The situation
The value was real It had nowhere to live
What already existed
Nari
Trusted voice
Teaching, public work, and lived experience in one presence.
Audience
Existing audience
A community already gathering around the work.
Knowledge
Recurring expertise
Workshops, materials, and explanations shaped by repetition.
Discovery material · Initial intake · recurring questions before formal method formation
01Collect
02Compare
03Cluster
04Synthesize
02The diagnosis
Behavior changed the read The read changed what we built
Parents arrived activated, scanning, and short on capacity. That behavior pointed to urgency rather than browsing. I ran the material through StrategyIQ, my method for pressure-testing a strategic read against evidence, and it changed the assignment: this was not an information problem to be tidied. It was a support problem, and support had to be designed for the moment it was needed.
SIGNAL
What we observed
Activated arrival, scanning behavior, and short capacity.
READ
What it suggested
Design for the moment of need, not leisurely content consumption.
DECISION
What changed
I shifted the work from organizing information to designing support under pressure: clear hierarchy, shorter quick-guide paths, and measurement shaped around urgent arrival rather than unhurried reading.
READ → DECISION
The first read identified emotional urgency. The closer read exposed a larger requirement: the experience had to respond as a connected system.
03Designing for the moment
Parents were not arriving to browse They were arriving in need
They were exhausted, emotionally activated, and often using one hand while caring for a child. That changed hierarchy, writing, navigation, quick guide length, illustration, and the choices offered next.
What the moment demanded
ExhaustedScanningHolding a childEmotionally activatedLooking for one useful sentence
What I changed because of it
Stronger hierarchy
Shorter intervention paths
Scannability
Quick guides
Navigation
Writing
Illustration
Support-choice architecture
Scannability is a form of care
REAL-WORLD USE
Short sections, strong visual anchors, and immediate next steps reduced the amount a parent had to interpret while already overwhelmed.
The competing priority was editorial completeness inside each quick guide. Evidence about the parent's state favored shorter paths and stronger hierarchy, so I accepted the tradeoff: depth moved into Aprende and later layers to keep the first screen usable under pressure.
04The learned identity
The identity had to learn before it could be governed
I designed five generations and kept every one of them. Each solved a problem the work had just revealed: recognition became urgency, urgency gained editorial structure, and structure eventually demanded rules for its own evolution.
Voice→Urgency→Structure→Formalization→Governance
A · Superseded
Recognition and voice
Earliest visual home for the voice · warmer than a finished practice.
B · Superseded
Urgency and intervention
Harder moments pulled the tone toward concentration and intervention.
C · Superseded
Editorial structure
Hierarchy and repeatable editorial patterns began to carry the work.
D · Superseded
Formalization and governance
Coherent enough to document publicly · still evolving underneath.
Current · Governed
Governed System
Lessons held together · a warmer system across editorial, product, and practice.
The iterations were not detours Each one encoded something the work had taught us
Once the practice began evolving through use, evolution itself needed rules
Internal
System of Record
The internal source of truth preserves decisions, lineage, migrations, and unresolved boundaries.
One source of truth
Historical lineage
Migration rules
Unresolved boundaries
INTERNAL · System of Record · Protected operating artifact
External
Public Brand System
The public system translates that truth into voice, typography, imagery, illustration, and implementation guidance.
Brand story
Voice & principles
Color & type
Photography & illustration
SHIPPED · criarsinculpas.com/brand · Warm Earth
05Visual support infrastructure
Some moments are documented Others have to be interpreted
Photography records lived reality. Illustration clarifies the emotional structure of a moment. Together, they help support feel human, recognizable, and usable.
Documentary, not marketing · the moment support becomes possible, not the moment it succeeds.
Illustration
Clarifies the emotional structure of a moment.
Un solo dibujo, cuatro distancias.
CineFotoPinSímbolo
HeartBrainSOSPause
ProhibidoPinClinical
El sistema no decora. Sostiene.
Visual production library
Eventually, even the imagery became a system
Assets were named and organized with formats, tags, transformations, and production references. New publishing could begin from a shared visual language rather than from zero.
One drawing, four distances · then named, tagged, and filed for production.
06From circulation to owned support
The feed surfaced the need The owned experience had to hold it
Nari's publishing exposed recurring questions and language in real time. I built durable places for those signals to land: immediate quick guides, deeper learning, and a path toward continued support.
A · Listen
SYSTEM IN THE MOMENT
Real social moment → structured support on the phone
DOCUMENTARY + LIVE PRACTICE
Cadence in practice · Recurring Reels and audience questions
Cadence
Publishing cadence designed around recurring Reels and audience questions
Questions
Editorial input
Responses
Support in circulation
Signal
What to deepen next
B · Owned layers
Need and experience, held on owned surfaces.
01
IN THE MOMENT
Immediate support
Quick guides offer a useful next step when capacity is low.
NeedUrgent
Four public quick guides shipped: Pantallas, Desbordes, Sueño, and Hermanos
SHIPPED
Quick guides · Intervention for low available attention
Act now → Understand next
02
SHIPPED
Aprende · Editorial depth on owned surfaces
BETWEEN MOMENTS
Learning
Editorial guidance helps parents understand what happened and prepare for what comes next.
ExperienceUnderstanding
Aprende · Editorial content · Method
03
OVER TIME
Deeper support
Deeper support creates continuity for needs that cannot be solved by an article or quick guide alone.
Agresión · Ansiedad · Límites
A concrete example of this layer is the classes currently in preparation for the next phase.
Next layer · Structured support · not yet shipped
C · Pathway
REAL QUESTION→PUBLISHED RESPONSE→SIGNAL→OWNED SUPPORT→PRODUCT LEARNING
07How we test, learn, and improve what matters
From quick guide to product signal
We were not publishing content. We were testing, measuring, and learning.
Evidence / Product signal
The strongest value was not more content It was practical relief, navigable language, and continuity
Use→Observe→Learn→Change
EVIDENCE
Testing plan · Free support experience → signals → deeper structured offer
Behavioral evidence
Four signals that changed what I built next
A 91-day reporting window is a small sample. It was still enough to correct two assumptions I had made about how this content would be used.
Evidence→Interpretation→Decision→Established
Entry signal
72%
Pantallas scroll depth
Evidence
Pantallas reached the site's highest average scroll depth, at 72%.
Interpretation
A familiar, immediate conflict became the strongest quick guide entry point.
Decision
Keep urgent, recognizable needs at the front of the public support layer.
EstablishedPantallas was positioned as a designed entry route into related quick guides, deeper learning, and later support pathways, an emerging progression, not yet a validated default across all traffic.
Depth signal
108sec
Desbordes attention
Evidence
Desbordes reached 79% average scroll depth and 108 seconds average time on page.
Interpretation
Parents did not only sample acute-support content. They stayed with it.
Decision
Prioritize concise intervention first, with enough depth to support understanding after the immediate moment.
EstablishedQuick guide pages were structured for rapid orientation under pressure, with denser explanation moved into Aprende and later layers rather than into the first screen.
Pathway signal
~30%
Portal entries
Evidence
Nearly a third of total traffic triggered portal entry during the reporting window.
Interpretation
A meaningful share moved beyond an individual page into the broader support environment.
Decision
Continue developing an owned pathway rather than treating quick guides as isolated content.
EstablishedThe information architecture connected quick guides to portal entry, learning surfaces, and an emerging path toward continued support, without claiming that progression is commercially validated.
Language signal
~21%
Visitors who changed language
Evidence
Approximately 1 in 5 visitors triggered a language change during the period.
Interpretation
Visitors actively used the bilingual capability.
Decision
Treat bilingual delivery as experience infrastructure, not a translation layer.
EstablishedLanguage became a first-class part of the experience. It shipped and is actively used, while broader distribution of that bilingual reach remains unproven.
Plausible Analytics · 91-day window · May 22–August 20, 2026
I initially treated the quick guides as educational content. Behavior showed that families reached for them as intervention tools, so I changed how I structured, measured, and maintained the experience.
08Behind the screen
The public experience was only one layer
Behind it, the practice gained the rhythms, responsibilities, production paths, workspaces, access systems, and measurement needed to keep the work moving.
Operating system
How the practice stays coherent over time.
OPERATING
Rhythm
I set a recurring rhythm that connects planning, publishing, review, and the next editorial decision.
SYSTEM
Governance
I wrote the rules: who decides what, what is allowed to change, and what has to stay stable.
SYSTEM
Measurement
Quick guides were structured to capture use signals such as views, time on page, and share actions, allowing future product decisions to follow behavior rather than assumptions.
Enabling infrastructure
The surfaces that make that practice runnable.
OPERATING
Production
I defined the path from signal to shipped support, so publishing no longer depended on improvisation.
OPERATING
Client workspace
Context, priorities, and active decisions moved into one continuous environment.
OPERATING
Protected access
The architecture could support continuity beyond public content.
09From support to product
Support needed more than content It needed a path into continued care
I architected the connection between free public resources, a calmer learning environment, targeted access, and membership. The value on offer is not premium content for its own sake. It is navigation, preparation, and continuity.
Understand what is happening↓Decide what matters now↓Take one useful next step
Architecture → Infrastructure
ARCHITECTED
Product architecture · Access layers made legible
IMPLEMENTING
Access infrastructure · Authentication and protected continuity
Member environment · In implementation
El Estudio taking form
IMPLEMENTING
El Estudio · Access → Member environment → Learning experience
Current state
SHIPPED
Shipped
Public bilingual platform
Four public quick guides: Pantallas, Desbordes, Sueño, and Hermanos
Editorial surface
Visual and illustration systems
Analytics instrumentation for the quick guide experience
ARCHITECTED
Architected
El Estudio product model
Access and permissions
Membership and monetization model
Measurement model
IMPLEMENTING
Implementing
Authentication and payments
Protected experience
Member infrastructure
STILL TO VALIDATE
Still to validate
Conversion and activation
Adoption and retention
Pricing
Commercial performance
The architecture is defined The infrastructure is catching up
What remains is implementation, adoption, and proof.
Shipped → Architected → Implementing → Validating
10What actually changed
What exists now that did not exist before
This is a living practice, not a finished portfolio artifact. Some capabilities are operating now. Others are architected, implementing, or still waiting to be validated.
The behavioral evidence, summarized
72%
Pantallas scroll depth
Strongest quick guide entry point · highest average scroll
108 sec
Desbordes attention
79% average scroll depth
~30%
Portal entries
Nearly a third of total traffic in the reporting window
~21%
Visitors who changed language
About 1 in 5 visitors used the bilingual experience
Plausible Analytics · May 22–August 20, 2026 · 91-day window
What the experience validated
The support content earned attention
Quick guide visitors showed strong scroll depth, sustained attention on Desbordes, movement into the portal, and active use of the bilingual experience.
What remains unproven
Distribution has not caught up
Of 223 visitors, 208 arrived through Direct/None. Instagram contributed 9 visitors, while Google and Bing contributed 2 combined. Early traffic remained concentrated within an existing network.
The early evidence validated the support experience, not yet its distribution.
What the engagement changed structurally
From presence-dependent expertise to governed support pathways
The work did not remove Nari from the center of the practice. It changed how her expertise could be organized, delivered, and developed beyond a single interaction.
Before the engagement
What the engagement established
Expertise concentrated in Nari’s direct presence
Expertise translated into governed support pathways
Support dispersed across social posts and messages
Support organized within owned, connected experiences
Publishing as the primary delivery model
Publishing connected to observation and learning
Decisions held through individual memory and effort
Decisions documented through rules, roles, and operating rhythms
Audience attention without a defined progression
An emerging pathway from urgent need to deeper support
Useful resources produced individually
A repeatable architecture for producing and evolving support
The result was an operating foundation through which the practice could deliver support, observe behavior, govern decisions, and develop future products without rebuilding each time.
Nari brought the parenting expertise, lived experience, teaching, audience, and trusted voice. Access still depended on her presence, post by post and message by message. I translated that value into brand, experience, product, governance, measurement, and operating architecture so it could travel farther.
The system did not replace her judgment. It changed how far that judgment could reach, how consistently it arrived, and how deliberately the practice could learn from what happened next.
WHAT CHANGED
The practice can publish, learn, and make decisions through a defined system.
WHAT BECAME POSSIBLE
Owned bilingual support and an emerging path from immediate relief toward continued care.
WHAT REMAINS UNPROVEN
Distribution, adoption, retention, pricing, and commercial performance.
This is the work I do at LG Studio: read a complicated situation, find the system it is missing, and build the thing that makes the expertise usable.
Nari’s trust now has infrastructure.
Living case study · April 2026 – August 2026 · Linked from Studio
NEXT
Building something that needs more than a website?
I help turn trusted expertise into clear experiences, useful products, and systems that can keep learning after launch.
