Permission to be wrong and slow
Oh, and behind on everything, too!!
Hello dear friends!
I have been DEEP in the weeds the last few weeks, designing and coding an early version of a tool to help you bulk print photos for your journal.
For context, a few weeks ago I posted this on my Pouch Instagram. I had made a few fixes to Journal Helper, and at the end of the post, I pitched a few new tooling ideas:
I wrote:
Personally as an analog journaler, I've been aching for tools like these:
š¼ļø Something to help you bulk-print (crop, resize, etc) photos for your journal
š Something to help you track and preview your analog sticker collection
LMK if either of these resonate with you, or if you have other analog journaling problems you'd love help with!! I'll be fiddling around with some ideas this month and next š
I got SO many comments on this (THANK YOUUU!!), and itās clear that thereās demand for a tool to help us bulk print photos.
Iāve been working on this bulk print tool for the last few weeks, and today I wish I was writing an announcement declaring, HERE IS A PROTOTYPE or something along those lines!!
But⦠itās not ready yet and I need more time.
GAH! I hate needing more time!! š
So today Iām going to tell this story: My ongoing attempt to accept the reality that, despite my best efforts to do things right and to do things fast, I will inevitably do things wrong and slow anyway. Despite my desire to be āon top of everythingā ā to keep up with news, to keep up with the stationery community, to keep up with texts and emails and DMs and newsletters and videos and events and parties and friends and family and everything else ā I shall, in fact, be ALWAYS BEHIND.
This is not a story of defeat, though! The more that I accept this reality, the freer I feel. Being wrong and slow and behind is not āfailureā because it is not skippable, especially as someone working solo and doing a lot of things for the first time ever.
Hope you enjoy todayās newsletter, and Iāll keep you updated on the tool! š
ā” vrk
š A case study in being unavoidably wrong and slow
Iāve already talked a lot in the past about how I designed covers for Pouch: Here I showed the redesign of Pouch Issue 1ās cover, and here, the process of designing Pouch Issue 2ās1.
Today I want to tell another Pouch cover design story, but from a different angle: Rather than focus on the design process, I want to focus on why my early mistakes were unavoidable.
Hereās the story of how I tried my best to avoid making newbie mistakes when designing my first cover of Pouch, and how I made all the mistakes anyway.
š SPOT THE DIFFERENCE
To quickly recap my past cover tales:
Pouch Issue 1ās cover took me 6 months to make, and the process was painful and frustrating.
A year later, Pouch Issue 2ās cover took me 1 week to make, the process was relatively smooth, AND the cover is (imo) much stronger than Issue 1ās.
Hereās a visual summary, too:
Upon hearing that Cover One took me 6 months of suffering while Two came together in just one week, a natural question might be, How could I have gone faster on that first cover??
What should I have done differently to get the results of Cover Two on my first attempt rather than a year later, and in 1 week rather than in 6 months?
If you look at the diagram above, youāll see that process-wise, I approached Cover One and Two in remarkably similar ways:
I started by sketching some possible covers.
From the sketches, I chose my favorite one, then I drew it properly.
Both times I made a first attempt to color the drawing, then after coloring, realized I needed to improve the underlying line art loll š
I improved the line art, then colored it again.
I finished the design.
However, with Cover Two, at this point of the process I had a result I was delighted with, but at this same point for One, I had a cover that I later realized didnāt serve me at all and that I needed to completely redo from scratch 3 months later.
So what the heck caused this difference??
š£ I didnāt know what I was doing
Well, quite simply, with One I didnāt know what I was doing, and by Two, I did.2
I can tell you now all the things the cover of a magazine needs to communicate:
Itās the at-a-glance introduction of your magazine to the world.
It explains whoās the audience for your magazine.
It expresses the tone and personality of your magazine.
Itās an expression of your brand. The cover of your latest issue becomes the symbol / icon for your magazine. Itās almost functions like a logo.
Of course, it also gives a preview of the content of this specific issue.
On top of that, thereās a lot to consider regarding the technical execution of the cover:
š¼ļø The composition of the cover must consider the composition of the drawing and the text at the same time. You canāt just make a āgood drawing,ā separately, and plop it into a ācover designā and expect a good result.
šļø The line art of the drawing needs to support the colors. A pen drawing looks totally different when colored. Mistakes are harder to hide, empty spaces are accentuated and, without care, the illustration can feel really flat.
šØ The colors, alone, tell its own story. You canāt just choose āgood colorsā for the cover; the colors can dramatically change what you end up communicating. Your colors must be in harmony with your message.
When I made Pouch 1ās cover, I had not internalized all of the above.
For instance, I had sketched several options for Cover One, but I didnāt know what a āgoodā cover was. I also didnāt know that I didnāt know this! At the time, I thought a cover just needed to be pretty, so I simply chose the āprettiestā sketch and I didnāt consider ācommunicationā at all when evaluating my options. Itās not surprising that the sketch I chose ultimately didnāt serve my communication goals ā at this point I didnāt know I had communication goals ā and so itās not surprising I later had to redo this cover completely.
But with Two, before I put pen to paper, I already had a much better understanding of what a cover needed to accomplish beyond looking nice. From that foundation, I could pick a sketch that served my goals much better, and I ended with a much better result much faster.
š¤·āāļø What would I change?
If I could go back in time and change how I approached Cover One, what would I do differently? What would I change?
A better question is, what could I change? And the answer to that is nothing.
The only thing Iād change ā the only thing I could change ā is my hubris in thinking there was any way I could do things ārightā on my first try!

I mean OK yes, in the last section I explained what I didnāt understand when attempting Cover One, and I claim this knowledge marks the key difference between past-me and now-me. But even if I could somehow send this information to me-of-two-years-ago, it wouldnāt have helped. Itās not like simply understanding a concept is the same as internalizing it and being able to execute upon it.
The hours and hours I spent on Cover One was not me being inefficient; it was me taking the time I needed to learn and improve.
Early in my journey to become a better artist & designer, multiple people told me the story of ā1000 pots.ā The saying goes, if youāre trying to master ceramics, you shouldnāt spend months trying to make 1 single perfect pot ā youāll end up with an overworked pile of clay, and a really bad pot. Instead, you should focus on making 1000 pots. Quantity over quality. By your 1000th pot, youāll be making pots perfectly.3
I heard this story and I believed it ā I still very much believe it!
Yet, despite knowing and believing the whole ā1000 potsā thing, I still spent waaaaaay too long spinning on the same design for Pouch 1ās cover rather than moving on and trying something new.
Yes, I realize this is super meta: Iām saying that even with the ā1000 potsā lesson, the parable that illustrates how you need lots of experience repeatedly doing a thing in order to master it, I NEEDED TO EXPERIENCE A FAILURE TO FOLLOW THIS LESSON in order to properly understand its message š
The actual act of drawing something, coloring it, and going WHOA that looks way different than I thought it would ā
The actual act of spending weeks finishing a cover that looks good but isnāt communicating what it needs to ā
The actual act of looking at the calendar and realizing HOLYYYY did I just spend 6 months on the SAME DESIGN???
These collective acts of trying and failing and making a million mistakes: This is the only path!
šŖ The permission to learn
Why am I talking about covers today?
In my intro to todayās newsletter, I explained the situation with my bulk print software tool. Iām currently in the weeds putting it together, and man, I really want to do things right and fast.
My burning desire to do things right means that Iām constantly questioning, āAm I doing things right??ā
Every step of the way, I second-guess myself. After the Instagram post, I wrote a simple product document outlining what might go into a bulk print tool:
Immediately after writing it, the cacophony of second-guessing began:
š¤ Everyone says when youāre designing products, you need to talk to lots of potential users first. Have I talked to people enough? Is it too soon to write a document like this?
š¤ Should I have done more user research before making these product decisions?
š¤ Should I have conducted interviews? But wouldnāt that take forever? Wouldnāt that be way too much talking and planning and not enough doing? Shouldnāt I be 1000 pots-ing this?
Next, I sketched some ideas in Figma for what the tool might look like:
The second-guessing swelled louder:
𤨠Am I ready to design yet? Maybe I should get feedback on my product ideas first.
𤨠Are these designs too high-fidelity? Am I zooming in on one design too soon? Should I make more possible designs?
𤨠Should I be getting design feedback before I continue?
After sketching one viable design, I decided to start coding a prototype:

The second-guessing has now reached max volume:
š§ Arenāt I coding way too soon???
š§ Everyone tells me that jumping to code too quickly is a mistake. This feels like ātoo quickly,ā right?? Shouldnāt I do more validation?
š§ But how do I do more validation? If my designs look bad, and I donāt even have a prototype, what the heck am I validating??
Meanwhile, in the background, my desire to move quickly is also shouting at me:
š£ļø ALL THIS THINKING IS SLOWING YOU DOWN
š£ļø YOUāRE SO SLOW
š£ļø GO FASTER
š£ļøš£ļøš£ļø GO!!!!
(It can be VERY LOUD in my brain sometimes!!! š)
I happen to be working on software right now, but my inner monologue sounds very similar to what I remember hearing while making Pouch Cover One: Why does this look so bad? Why are you doing everything wrong? Why are you going so slow?
But I can look back and know now, with confidence, that there was no other path for Cover One. I made mistakes because I didnāt know how to avoid them yet. I went slow because that was the only speed available then.
As I write my software and hear these familiar voices in my head, Iāve found that this time I can speak back to them. I find myself repeating, like a mantra, āItās fine. Iāll just do it wrong and slow. Itās OK to be wrong and slow.ā
And, āThis is the learning. You canāt skip the learning.ā
I really wasnāt being facetious when I said if I could change one thing about how Pouch Cover One went, itād be to confront my hubris that expected me to do things right the first time ā the hubris that thought I could somehow outsmart the whole ābeing a beginnerā thing. This is what I want to do differently: I want to give myself permission to take the time I need, make mistakes, and learn.
Iāll do things right once I learn how to do them right. Iāll do things fast once I learn how to do them fast. In the mean time, Iām⦠just gonna do it!!!
š PS: Iām also behind on everything
WELL!
A consequence of doing things wrong and slow is Iām also way behind on everything I want to get done lollll.
But I reiterate: This is not a story of defeat!! Itās a story of acceptance.
What changes when I accept being wrong, slow, and behind on everything?
I am physically a lot more comfortable š Iām less stressed about all the mistakes Iām making, how slow Iām going, and how behind I am. Itās happening and itās unavoidable! Thereās no need to stress; this is all to be expected.
I have more energy. Iām spending my energy planning for this reality rather than wasting my energy trying to prevent it from happening.
I say no to way more things. I NEED to protect my time. Because not only do I need time to make things, I need time to make things slowly and incorrectly and then I need even more time to go back and fix my mistakes. That means I MUST clear my calendar to focus on building software, even if that means dropping a lot on the floor. For instance, I havenāt posted on Instagram in 3 weeks ā oh well!! My Substack is a bit late ā oh well!! I canāt work on Pouch 3 right now or other related fun things ā bahhhhh I wish I could but I canāt!! Iāve had to say no to some exciting opportunities with Pouch because I canāt right now! I need time!! I need to be extremely selective with how I choose to spend my time, forgive myself for dropping the ball constantly, and let go of FOMO. I canāt do everything. Actually itās more extreme than that: In order to have time to do just one thing well, I need to do very little else.
Yet Iāve also given myself more time to meander. This point is weird and contradictory to the previous one, but⦠I notice I am also more open to the occasional meandering. Within reason, of course!! I still gotta make sure Iām spending enough time doing the thing. But when I know that Iām gonna be wrong, slow, and behind anyway⦠I can let go of discipline and follow my zoomies sometimes!
Iāll leave you with two such meanderings from last month.
š² Two meanderings
1) A talk I didnāt give
In June, there was an event for a ācreative technologists show & tellā happening near my apartment. I felt the urge to give a tech talk for the first time in years! Specifically, I wanted to give a tech talk presenting Pouch magazine as a technical product, because that is another angle through which I view Pouch myself.
I prepped a talk, but the event ended up not being a good fit for it, so I dropped out.
Still, Iām proud of the talk I cobbled together!
The talk: https://vrk.mmm.page/jun0305-demo
Itās pretty easy to follow along if you want to read the presentation. Iāll work on it again at some point, probably when I have an appropriate venue for this. Feel free to comment below or reach out if you have any ideas!
2) A zine for a friend
My friend Michael Hsu became a US citizen last month, and he and his partner Julia invited me and other friends to witness the occasion. It was a complex day, as the nature of the task, especially at this particular moment in America, felt equal parts celebratory, unsettling, and absurd.
But there was an unambiguously fun aspect of the day: Because phones arenāt allowed in the courthouse, we drew pictures to capture what happened!
The day had so much meaning and emotion, and our drawings were so fun and lively, I felt the urge to capture it in a zine! I combined the drawings along with quotes, photos, feelings, and memories from the day to create a zine called HSU-S-A.
I printed 20 copies and gave 15 to Michael & Julia, kept 5 for myself and fellow zine friends. Itās not for sale, but you can read most of it below.
Read HSU-S-A: https://leaflet.pub/f35bca05-1cf5-4e32-b51f-e1168bca1f8f
It felt wonderful to take time to celebrate a dear friend of mine, and to make something to help us collectively process and remember the moment. We love you, Michael!! š
Alright, thatās it for today! Iām going to do some stretching and get back to coding. Tool ready soon, I hope!! Well I guess if I learn my own lesson, itāll be done when itās done š
Till next time!! š¤
Though, misleadingly, my essay literally entitled How to draw a cover is not really about drawing covers lol
Probably obvious but Iām not trying to say that Pouch Issue 2ās cover is PERFECT and now I know EVERYTHING there is to the art of cover design š I am still, all things considered, a beginner to the craft. But I have a significantly better grasp of what Iām doing than I did before!!
Tried to find the history of this parable, and many people online attribute it to this quote from Art & Fear. But in my reading of it at least, it seems like Art & Fear is also retelling an old parable, so I suspect thatās not the origin of it, either. Let me know if anyone can confirm or deny!









I love your dispatches Victoria and this is no exception! That voice yelling at us to go faster is not only from general capitalistic culture but also tech/eng culture expecting quick MVPs and iterations. It takes so long to unlearn that and learn to move at our own pace again. I admire the slowness and focus you're adopting lately, turning down other opportunities and friend hangs and such! Otherwise the overwhelm can really drown us š°
Thank you for sharing your experience and the lessons learned. The inner monologue with the emojis š¤š¤Øš§ is so relatable. I read this today as Iām scolding myself for ānot doing enoughā or ānot doing things well enoughā, but your writing helped remind me that Iām doing a lot of things for the first time this year. What matters is that I keep going/trying, which I am!
Looking forward to the software when you feel itās ready. Iām excited to see it in action!