Hey there, we’re the MojoTech Design Team. We are kicking off a new series as not only a fun activity for ourselves but hopefully helping end your week with something interesting. Each week we’ll share what we found inspiring, helped us learn something new, or anything else that struck our fancy.
Shifting to remote work has meant needing to rejigger my own feedback loops. Exponentially more Zooms and Google Meets disrupt my work flow and make tracking or understanding progress more difficult, as those blocks of dedicated time have gotten more atomized. The “microtasking” and feedback mechanisms Lara outlines have been a really easily implementable bit of structure to keep things feeling like they’re moving. I’m deeply grateful to have that scaffolding ready for working on more product concept or discovery projects, where the abstracted nature of the work makes it harder to quantify upfront than counting up completed Jira tickets.
This post was new to me and shared by some folks on the team. We decided to take a look at our current meetings, agendas and routines and make some changes. We’re now kicking off the week with a Warmup meeting, making better use of our critique scheduling, and ending with our Friday hangout. Along with this post we started using a few new tools like Around for quick, distraction free video calls, and Navigator to collaborate on meeting agendas. I’d recommend giving this a read and doing some spring cleaning on your internal communication process.
For the last few months, I have been neck deep in front-end code helping a client ship a completely redesigned website. I like it here, I enjoy working with code. Whenever this happens though, I make it a point to get some exposure to some good ol' capital "D" design. This is important to me becuase it helps me feel balanced, and I like to think it keeps me from getting too rusty when I am inevitably back doing proper design. While searching to scratch this itch, I stumbled on this wonderful newsletter about, well "Frank Ocean’s $150,000 sofa, an underrated Richard Neutra house, musings on the best mid-century daybeds" and other very niche and design centric topics. It's an easy read and who doesn't like staring at aesthetic furniture and decor? Give it a go.
Two things have been on my mind this week: this clip of John Mayer asking you not to use free fonts, and a recent podcast by Postlight on what C-suite stakeholders care about.
I’ve been working with the innovation team of a large company recently, so I’ve been in the world of org charts, multi-step approval processes, and competing organizational goals. It’s all reminded me of how critical it is as a designer to be able to translate your decisions into the language and values that stakeholders understand. Postlight’s founders dive into these values in a way that’s both engaging and clear.
As someone who is typically working on the front-end side of things I’m always on the lookout for new tools to help streamline implementation. Recently an engineer on the team showed me Design Tokens. Design Tokens is a Figma plugin that exports theming values directly into a json file. Designs change over time and sometimes you can end up with messy theme files consisting of either outdated values, or just wrong values that got lost in the shuffle. When used in conjunction with Style Dictionary library you can transform the Design Tokens output into a format you can consume on any platform.