Studio
We build trust. It starts with understanding.
In Bogotá’s fast-moving tech scene, users are often asked to adapt to product logic. We reverse that dynamic. Our work is grounded in local context and built to meet global usability standards. A focused team of five specialists, working from a workspace designed for deep collaboration.
Our Chapinero studio. The 'research wall' is visible to the left. We map user journeys here to keep context visible and shared.
The Bogotá Creative Engine
Our location in Chapinero isn't incidental. It’s a deliberate anchor. This district sits at the intersection of Bogotá's established creative energy and its emerging tech hub. We draw our methodology from the city's dual nature: the rigid, historic grid of La Candelaria’s streets and the organic, flowing lines of the Andean landscape visible from our window.
This informs a core tenet we call ‘Local Context, Global Standards.’ We don’t just translate Spanish interfaces. We design for Colombian user behaviors—how people manage mobile data, trust new payment methods, or prioritize speed over depth. Yet, we benchmark rigorously against international usability heuristics. It’s a synthesis, not a compromise.
“The research wall isn’t for decoration. It’s our single source of truth. If a design decision can’t be traced back to a user quote or a behavioral pattern on that wall, we question it.”
Our studio is intentionally small: five full-time specialists. This isn’t a constraint; it’s a design choice. Deep collaboration is non-negotiable, and creative oversight is consistent from initial sketch to final handoff. The workspace is flexible, featuring areas for silent deep work and a dedicated table for client workshops where we co-create, not present.
Our Design Principles, Annotated
Friction as a Signal
Every hesitation or drop-off in a prototype is a data point, not a bug. We pause to investigate, often uncovering a mismatch between user mental models and the proposed interface.
Why it matters: It moves us from subjective opinion to observable evidence.
Content-First Architecture
We structure flows around the user's narrative—what they need to know and do, in what order—before considering any visual components or framework constraints.
Why it matters: It prevents the container from dictating the content, reducing cognitive load.
Performance as a Feature
Load times and interaction latency are designed into the prototype. We test on representative devices and network conditions, treating speed as a core usability metric.
Why it matters: In markets with variable connectivity, performance is accessibility.
Accessible by Default
We build with WCAG 2.1 AA as a baseline in our component library. It's not an overlay; it's baked into color contrast, focus states, and semantic structure from the start.
Why it matters: Retrofitting accessibility is costly and often incomplete.
Iterative Fidelity
We avoid a purely linear path from sketch to hi-fi. Lo-fi and hi-fi prototypes run in parallel for core flows, allowing us to test visual impact and interaction logic simultaneously, not sequentially.
Why it matters: It catches usability and aesthetic mismatches earlier, when they're cheaper to fix.
The Trade-off Frame
Good design is a series of conscious choices. Here are ours, with the inherent compromises.
-
Speed vs. Depth of Research
We sometimes extend discovery phases beyond client budgets. Mitigation: We deliver a clear memo linking additional research days to specific risk reduction.
-
Custom Illustration vs. Development Speed
Unique imagery creates brand depth but adds time. Mitigation: We use a mix of custom and high-quality stock, with a clear rationale for where custom is non-negotiable.
-
Complex Features vs. User Clarity
Feature-rich products can overwhelm. Mitigation: We use progressive disclosure and user testing to validate each added layer's necessity.
Pitfalls to Avoid
Based on work in the Colombian market, here are common mistakes we steer clients away from.
Ignoring Mobile Data Constraints
Designing only on fast office Wi-Fi leads to image-heavy interfaces that fail on 3G.
Over-reliance on Global UX Patterns
A pattern that works for a US user may confuse a user accustomed to different digital rituals.
Treating Accessibility as a Final Check
This is expensive and often results in a compromised, patchwork solution.
Our Lexicon
A few terms we use with intention.
- Context Pattern
- A design solution specifically proven to work for our local user base, documented in our internal wiki.
- Ghost Metric
- A vanity metric we teach clients to ignore in favor of more meaningful engagement signals.
- Fidelity Lag
- The gap between a prototype's visual polish and its functional reality. We aim to minimize this.
- Local Friction
- Friction that isn't a bug, but a feature reflecting a user's legitimate caution or cultural habit.
A Moment of Realism: The Cart Conversion Problem
A local Bogotá e-commerce client saw 70% mobile traffic but high cart abandonment. Initial hypothesis: the "Buy Now" button was too small. In user testing, the issue was more nuanced. Shoppers hesitated because the final price didn't clearly break down 'Envío' (shipping) vs. 'Precio Final'.
We didn't just add a breakdown. We designed a full-screen summary card on mobile that appeared on scroll, using a familiar UI pattern for totals. It introduced one extra tap but removed mental calculation.
"The 'fix' wasn't technical. It was empathetic. We respected the user's need for clarity over the developer's desire for simplicity."
This is the outcome of a design process that treats hesitation as data, not a flaw. It requires time to observe, not just to build. It's the value we promise and the constraint we work within.
Ready to explore a project?
Our next step is always a conversation. Share a brief, and we'll respond with a proposed path forward.
Calle 62a sur #66a-50
Bogotá, Colombia
+57 318 190 3088
Mon–Fri: 9:00–18:00