There is never a ‘good time’ to do research, but we can at least all agree when and why it is necessary for strategic product decisions. What happens when the only research you can fit in your project is remote – with participants and with a co-located team? Before you cringe, pull your hair, or just laugh – here are some techniques we learned during our recent engagement with DailyPay.

It’s a simple idea that can help your digital product take shape; when a user enters your system, do you hand them a map or a path? What’s the difference? Great question, and in this case, the metaphor is pretty literal.

So you want to grow your product? That’s super awesome. Growth is often a goal that startups rush towards. 

“We need 100,000 monthly active users yesterday.” – random startup person 

Growth can mean a lot of things. Maybe you’re trying to grow the number of users, or increase time spent using your product. Whatever it is, growth usually means moving metrics. But meeting your growth goal takes a very meticulous and strategic design process. You need to try out ideas and see what actually works. In this article, I am going to share how to set up a successful experiment-driven design process that can help you identify the features and changes to grow your product. Let’s grow!

The primary function of design is to make something useful. Unfortunately, many digital products out on the market have been developed without universal accessibility in mind. As designers, we have the unique opportunity — and responsibility — to help shape the next generation of inclusive and accessible technology. 

It is a delight to use software that seems to really ‘get’ you as a person! To achieve this, it requires that the software has been built by people who sought out to understand their users. When software isn’t built with its users in mind, it has the potential to leave its users feeling alienated. In this post, we’ll be exploring a seemingly simple item we often put on forms that is very easy to get wrong: the gender field.

On Wednesday night, designers and design lovers from all over NYC gathered at Carbon Five SoHo to receive career guidance, feedback, and insights from five senior designers. The evening kicked off with a Q&A with our panelists:

• Lo Wheelwright, Senior Product Designer, Carbon Five
• Erin Murphy, User Experience Designer II, HBO
• Nina Mehta, Design Manager, Mailchimp
• Mumta Mittal, Product Designer, Knotel
• Christopher Seeds, Senior Product Designer, Blackboard Insurance

How can scaling companies maintain design consistency and quality as internal and engineering teams exponentially grow?

Last week, Carbon Five San Francisco hosted Talk Night to answer this question and to discuss the secret benefits of building design systems for growing companies. Our guest speakers included:

• Sean Durham, Software Development Manager, Autodesk | @seandurham
• Erin LaPorte, Product Designer, Mixmax | @erinlaporte007
• Andy Tran, UI Engineer, Mixmax | @helloandytran

Five Ways Junior and Senior Designers Can Work Together Effectively

Disclaimer – I am a designer so this is written for /designer pairs but it’s also relevant for any other Junior/Senior duos.

Hello, wonderful Junior/Senior design duos! Odds are you are fairly new to working together. Perhaps the junior designer is fresh out of school or the senior designer just got a promotion. Whatever the circumstances are, you are now buddies and will keep working together. So, let’s make sure that it is awesome!

This is the journal of two LA designers attempting to host a drink and draw series. But to start – why a drink and draw? As designers in an office of 20-ish developers, we felt lonely (or insane) cooing over our own grid paper. Some days felt like far too much screen time and an outright neglect of the peaceful ritual between pen and paper. We also like to drink. So in the spirit of team-bonding, an hour dedicated to both seemed like a much-needed refresher.

Enter our experiment: The Drink and Draw

Arguably the most difficult skill you’ll learn in your design career is how to communicate that you did what you set out to do in a way that gets people to support and continue the work you did.

Presenting design successfully is about knowing what you want out of the meeting and structuring it to meet those needs. There’s a cliche of design reviews as interpersonally fraught spaces where stakeholders alternate between going on tangents and ripping your work apart. It doesn’t have to be that way.