Craft is the foundation. System is the multiplier.
We obsess over every pixel - that's non-negotiable. But pixels alone don't scale. We build operating systems for design delivery - intake paths, brief standards, feedback protocols, packaging rules, shipping cadence - so that premium quality repeats itself without heroics.
Cadence beats urgency. Every time.
"ASAP" is a signal there's no system. We replace fire drills with weekly rhythm - predictable load, predictable output, predictable quality. When there's cadence, "urgent" goes back to being an exception.
Premium is a standard, not a personality trait.
Quality doesn't drop because people lack skill. It drops because everything becomes ad hoc. We build the templates, checklists, components, and handoff packs that make premium repeatable - across every team, every project.
Calm execution is the real competitive advantage.
Teams don't want "fast". They want fast without chaos - where approvals don't turn into drama, standards stay consistent, and nothing depends on panic and heroics. Calm is engineered, not wished for.
Close loops. Early. Every time.
Open loops are the hidden tax of modern work: briefs without success criteria, feedback that's just a feeling, "final" that never becomes final. Speed without burnout comes from closing loops - on purpose, every time.
Structure creates freedom. Not the other way around.
Remote work isn't the problem. Lack of structure is. When intake, decisions, feedback, and shipping have clear rules, creative energy goes into the work - not into coordination overhead.
The work speaks.
I don't have to.
Reszek · remote
I've been designing for fifteen years and most of what I learned came from watching beautiful work get killed by bad operations.
Before design, there was breakdance. Around the millennium I stood in the cypher as a b-boy - and battles teach you things no design school does: show, don't talk. Freestyle only works on top of fundamentals you've drilled a thousand times. Twenty-some years later, that's exactly how I run production.
I started at Deloitte Digital. Then came the expat years - six years, five cities, five operating cultures. Kubota, Dawid Podsiadło's tours with Muzk, Pelion in between. Bigger stages came next - FIFA, UNIQA, blockchain during the web3 wave. Different industries, different agencies, different scales - but always the same pattern. Senior designers stuck in revision loops. Briefs that needed three rounds before anyone could ship. Brand consistency leaking across locations nobody had time to audit. Strategy meetings interrupted by “just one more banner.”
Eventually I stopped accepting that as the cost of doing design. I built r3loop - a methodology that treats design ops as an operational system, not a personality trait. Sonova, Benefit Systems and Archicom became the first clients - and most partnerships that start here don't end: the average now runs 5+ years. Eight steps that turn creative chaos into a working system - at every scale, from a single brand launch to 250+ locations.
EU-based, remote-first. Working with 5-10 brands at a time on retainer, plus running two of my own SaaS products on the side (Caterelo, regional.fit). Methodology you sell needs to survive your own use of it.
I write occasionally about what scales and what doesn’t. Reach out: hello@r352.com
We'll make it look good this time.
We'll build the system that makes it look good every time - across every team, every launch.
Send me the brief whenever.
One intake path. One brief format. One decision owner. Always.
We're flexible and available.
We ship every week. Feedback has windows. Cadence is non-negotiable.
We'll handle whatever you need.
We diagnose your delivery bottleneck first, then build the system that removes it.
We move fast and break things.
We move at a sustainable rhythm and ship things that hold.
Here's a beautiful deck. Good luck scaling it.
Here's the design and the operating system - so it scales itself.
Your design pipeline should run like infrastructure - not depend on heroics.
We work with organizations that need design delivery which scales without losing quality, speed, or sanity.
Every engagement starts with a diagnostic.
We don't guess. We map your current delivery flow, find the bottleneck, and build from there.
One decision owner per workstream.
If nobody can say yes or no, feedback never ends. We require clarity before we start.
Weekly shipping cadence.
Every week, something real goes out. Not "progress". Output. Publish-ready, packaged, named, spec'd.
Feedback has structure.
Feedback happens in windows, with criteria, in a format. Not as a constant stream of feelings across DMs.
We build systems, not dependencies.
When we leave, the operating model stays. Templates, components, checklists, quality rules - all yours.
Responsiveness ≠ availability.
We clarify fast, align decisions fast, deliver the next usable step fast. We don't sit online 12 hours.
A note on craft
In the era of AI output, craft matters more.
Typography. Spacing. Hierarchy. Micro-decisions. Details are not decoration. They are signals of discipline.
Systems create structure. Craft protects standards.