The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
How I Approach Operations & Documentation Cleanup
When supporting small teams, my focus is always clarity and follow-through.
I start by reviewing existing documents, trackers, and workflows to identify gaps, duplication, and friction. From there, I simplify processes, clarify ownership, and document what actually needs to be repeatable.
My goal is not to over-engineer systems, but to leave teams with clear processes, organized documentation, and lightweight reporting they can maintain.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
I was on a client call today explaining why I went with a certain brand direction and halfway through I realized I wasn't explaining anything. I was figuring it out on the call.
Like.. the strategy doc exists and the rationale is in there. but the thing that came out was even better than what I had, and I think that's because I had to make it understandable for someone who's not in my head for 3 weeks.
Not sure if that's a bad thing or not? I think the reason presenting design work feels awful sometimes (at least for me) is because my thinking isn't done yet and I can feel myself finishing it in real time and there's nowhere to hide.
I've been trying to just... accept it? Like, stop treating the presentation as the thing after the work. It might be the work.
Still figuring that out tbh
It's for sure really hard to present design decisions when we feel as if nothing is ever considered "done". I think designers index pretty high on the perfectionism scale which makes it so difficult to feel like anything is ever complete. I think putting ourselves in positions...
Punch: Designing a structured product for parcel booking and tracking.
Most logistics products don’t fail because of features.
They fail because the system behind the experience isn’t clear.
For Punch, the goal was to build from the ground up:
Product frameworks
App design system
A clear user flow for booking and tracking parcels
The focus was simplicity — allowing users to create delivery routes and track parcels seamlessly using a registered Delivery ID.
Every decision was made to reduce friction and improve clarity across the experience
If your team is making decisions off gut feel because the data is too messy or too slow — that's what I fix.
I'm a BI engineer specializing in logistics, field operations, and multi-country businesses. I've spent years building the data infrastructure for companies with distributed fleets, regional agents, and operations across multiple markets.
What I deliver:
→ Metabase dashboards your ops team will actually open every morning
→ SQL data models that don't break when your data grows
→ Automated reports that replace hours of manual work
→ BI infrastructure that scales with your operations
I work best with startups and scaleups that have real operational complexity — you're past spreadsheets but not ready for a full data team. I can be that team.
No commission taken. Direct contract. Let's talk.
Trending
Figma Make
Go from idea to prototype in minutes. What are you designing?
aivideo
AI video tools are moving at warp speed. Which ones are you experimenting with?
illustration
Handcrafted illustration is bubbling up across the web. What are you drawing lately?
aidesignflow
AI tools are redefining design work. What's your current workflow?
freelancerlife
Freelancer life is wins, pivots, and everything in between. What’s yours right now?