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
I’ve sat through countless meetings that should’ve been an email.
This explains why meetings fail, and why design matters even more than attendees:
1. Meetings aren’t always necessary: many problems don’t require real-time discussion and work better asynchronously.
2. The problem is design, not people: meetings fail when purpose, structure, and outcomes are unclear.
3. Good meetings have one clear goal: they define why they exist, who needs to attend, and what decision is needed.
4. Status updates waste time: sharing information rarely justifies a meeting.
5. Meetings are products: when designed intentionally, they become fewer, shorter, and more effective.
Design meetings that earn the time they take.
Source: Article
forbes.com
The Science of Meetings That Actually Work
An organizational psychologist explains why most meetings fail and the science backed principles leaders can use to run meetings that get results.
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
Last week we hosted the first Framer event in New Delhi and the first event I've ever hosted.
I know the merch was probably your favourite part. But mine was watching a room of designers, developers and founders go from quietly listening to genuinely talking. Client stories, workflow debates, real questions.
The kind of conversation that doesn't happen on a Slack thread.
That's what made it worth doing:)
We covered @Framer end to end; its evolution, its real capabilities, the code side, the design side, and what it actually looks like when you push it in production. At some point someone asked whether CMS work requires code.
The clearest answer was just opening @Framer and building it live.
It was fun diving into how we use @Framer at Formeta Studio for the animations, the component builds, the things that look like they needed a larger team.
They didn't.
Two people, a writer (Chhavi) and a designer (yours truly) built all of it:)
That's the part about Framer that's hard to explain until you see it. The gap between what the output looks like and what it actually took to build. That's where the tool earns its place.
Grateful to Daksh and Abhishek for bringing their perspectives, and to @Framer for making this official.
Hope you took home more than just the merch 😬
5 design books that changed the way I think 🧠✨
Not “pretty UI” books. Not “which font should I use?” books.
These are the books that made me look at design as a way to understand people, solve problems, and build products that actually make sense.
📞 1. The Design of Everyday Things - Don Norman
The book that explains why we push doors that should be pulled and why it’s usually not our fault, but bad design.
🧩 2. Don’t Make Me Think - Steve Krug
A classic reminder that users don’t want to “figure it out.” They want products that feel obvious from the first click.
⚡ 3. Sprint - Jake Knapp
For everyone who has ever spent weeks discussing an idea instead of testing it. This book shows how to move faster and smarter.
🌀 4. How to Make Sense of Any Mess - Abby Covert
Perfect if you work with chaotic projects, messy information, or unclear structures. It teaches how to turn confusion into clarity.
🔥 5. Design Is a Job - Mike Monteiro
Honest, bold, and a little brutal. A book about clients, value, responsibility, and why design is not just about visuals.
These books changed my mindset from:
“I need to make it look good” to “I need to make it work, feel clear, and create value.”
What design book changed your mindset?
Share yours in the comments 👇
Recently I’ve started prototyping my designs in Figma more than I have in the past.
I tended to avoid prototyping in the past due to it being time consuming and honestly most of the projects I was working on were simple enough to not require this amount of detail.
But as the projects I work on have become more complex I’ve found that this extra attention to detail really helps align with stakeholders and sell them on a design before starting development.
With a prototyped design clients are able to interact and see how the website will function, not just how it will look. This helps reduce uncertainty in the final deliverable and ultimately helps speed up Webflow development.
In the past describing all the hover interactions and click interactions for something even as simple as the slider below would require both time for me to explain and some imagination on the client’s part.
While imagination is great, it’s not the best way to align on fine details.
Anyways, long story short, new policy is show don’t tell.
Trending
Runway
AI video generation is exploding. What are you dreaming up in Runway?
Contra University
Learn from expert creatives how to earn more using next-gen AI tools.
creativeaiflow
Creative AI workflows are evolving. What tools do you use, and what are their strengths and weaknesses?
portfolioreview
The best portfolios tell a story, not just show a grid. Share yours for feedback.
freelancerlife
Freelancer life is wins, pivots, and everything in between. What’s yours right now?