DesignOps

Introduction

During my time at SkillsEngine, I took a strong initiative to develop scalable DesignOps frameworks that foster a mature culture of collaboration and knowledge sharing.

Part of my initiative, I introduced:

1. Hot Coffee Sessions: Monthly sessions for all company member to join, have some fun and learn something new about our (future) designs, learn something new about the design practice and learn something new about our users (data & insights updates or market research). It is less formal than a company standup.
2. Led the strategic onboarding to Figma and handoff process, while overseeing the cross-functional collaboration, enhancing design delivery process component adoption rates.
3. Introduce Crit sessions and methods
4. Project managed the release and updates of our Support Docs, including written documentation, loom videos and design mockup.

Hot Coffee Example:

‍

How we work on Figma:

‍

Crit:

I take a lot of pride in developing DesignOps frameworks that foster a mature culture of constructive critique, collaboration and knowledge sharing and critique methods.  

Here is my particular focus on the approach to design critiques.

The True Purpose of Design Critiques

I view design critiques as much more than just a feedback session. While critique is certainly a crucial component, these sessions serve a broader purpose. They're an opportunity to share work, discuss blockers, and exchange ideas. Most importantly, they're a vehicle for sharing knowledge, including the small decisions that shape our product.

I believe that to be effective contributors, designers need to be subject matter experts on our app. How can they achieve this expertise if they don't understand the reasoning behind even the smallest feature decisions? Design critiques bridge this knowledge gap, ensuring that our entire team is aligned and informed.

Cultivating a Positive Critique Culture

When executed well, they foster collaboration, build trust, and drive continuous improvement in our designs. However, we're acutely aware that poorly managed critique sessions can lead to frustration and become "just another meeting" to endure.

To ensure our critiques remain valuable and engaging, we've developed three primary approaches: Weekly Crit Sessions, Silent Crit and Jam Sessions.

1. Team Critiques

For team critiques, I like to set a framework where we can submit sharing objectives ahead of time. This also helps create a meeting plan. Before diving in, we establish who will be sharing and what specific feedback they're seeking. This approach ensures that initial feedback is targeted and relevant, though we encourage additional ideas and questions after addressing the primary objectives.

Key tips for sharing:

• Share relevant context ahead of time
• Have a specific feedback ask
• Be vulnerable
• Share blockers or challenges.  It is okay to say I don’t know what to do…yet.
• Ask specific questions

Key tips for giving feedback:

• Encourage consistency when it comes to UI feedback
• Ask probing follow-up questions
• Be clear if you are giving general comments or concrete suggestions
• Use the “I” perspective.  If you find it confusing, say that “I find it confusing” and not this flow is confusing.  Give the presenter a chance to share more context.
• Crit can mean praising.   It doesnt need always need to be about the questions or concerns
• Don’t multitask.  Be present or just let the team know that you need to miss this session to finish up work related to an upcoming deadline

Managing Crit is also really important.  Let’s check in on what was shared last week.  If someone mentioned they will look into an idea that was shared, let’s follow up to make sure feedback is heard.  It is also a great way to evaluate the type of feedback we are giving and how it is used.  

2. Silent Critiques

I’ve also embraced the concept of "silent critiques" aka commenting on Figma.

While it might seem daunting to log into Figma and see a flurry of comments before your morning coffee, I’ve found this approach incredibly valuable. It demonstrates that your teammates care deeply about the product and your work, offering insights, asking questions, and identifying potential edge cases you might have missed.

The Power of Constructive Feedback

It is important to emphasize that critiques are not about criticism, but about collective improvement. When a teammate takes the time to provide thoughtful feedback, it's a sign of respect and dedication to the product's success.

By fostering this environment of open communication and collaborative improvement, I’veseen remarkable growth not just in the quality of our designs, but in the strength of our team bonds and the depth of our collective product knowledge.

And make sure to Crit the Crit. The way we work can always be improved.

3. Jam sessions.

This one is simple.  If you don’t want to present a design challenge or ask for specific feedback but want to jump into Figma together, jam as if we were on a whiteboard in the office, just ask. 

Schedule a jam session and let’s design together on Figma.  Sometimes 5 minutes will go by in Silence but then the conversation can pick up to ask a question.  Silence is okay.

Read more about a longer jam session: 4 Step Brainstorm

‍

Support Docs:

Click here to view an example on our help center: https://www.skillsengine.com/se/managing-an-organization-on-skillsengine/

‍

‍

Responsibilities

• Served as a key strategic partner to the CEO and Head of Engineering, balancing long-term AI innovations with short term tactical product delivery.
• Developed scalable DesignOps frameworks that fostered a mature culture of constructive critique by standardized knowledge sharing and critique methods.
• Led the strategic onboarding to Figma, resolving handoff inefficiencies while overseeing the cross-functional collaboration, enhancing design delivery process component adoption rates.
• Championed Design Thinking principles across the team, fostering professional growth and mentorship resulting in an increase in user-driven features and design-led projects
• Pioneered end-to-end product strategy for a Stripe API-powered payment ecosystem, streamlining plan management and billing while reducing support queries and manual onboarding.
• Fostered a startup-like innovation environment while addressing complex technical problems with strategic decisions on design priorities and trade-offs within a 12-week Shape-up cycle. 

‍