Kevin LanceplaineFeb 4, 2023
Sho Kuwamoto

Question for #figma users..

Over the years, we’ve gotten into the rhythm of doing bigger feature launches at our annual Config conference.

Is this…
a) good because it’s exciting
b) good because having feature releases lumped together is less disruptive to day to day work
c) bad because it’s more fun to have features coming out here and there every month

Wdyt?

Feb 4, 2023 at 7:28pmMastodon for iOS
Show threadTaimar TeetlokFeb 4, 2023
@skuwamoto Exciting for sure but getting hands on new features and improvements as soon as they’re ready is more practical and helps to make a difference sooner.
Show threadJipFeb 4, 2023
@skuwamoto I want the good features as soon as they're ready! If there's a way to improve my way of working, it's great to have that as soon as possible
Show threadJFeb 4, 2023
@skuwamoto I enjoy the current release pattern. Exciting big features at Config, but lots of smaller quality of life improving features sprinkled throughout the year.
Show threadbenFeb 4, 2023
@skuwamoto c) for me personally. it’s something i appreciate about discord.
Show threadRadleyFeb 4, 2023
@skuwamoto I think introducing a tentpole or advanced beta feature works great. Anything more falls below the fold.
Show threadKevin LanceplaineFeb 4, 2023
@skuwamoto [A.] It’s very exciting to discover and learn about features during conferences. Much like Apple events. Ideally not just once a year but a few times a year, similar to Apple that has big keynotes each year.
Show threadAdrian Mato 🐙Feb 4, 2023
@skuwamoto I always feel that destroys tempo and puts the highlight in announcing the next big thing rather than incremental improvements with a good cadence
Show threadSteve ZimmermanFeb 4, 2023

@skuwamoto (B) + an option on when to accept those updates.

When you use a tool to get things done, it can be frustrating to have the deck chairs moving around on you (even if they are really nice and exciting deck chairs).

Bulking launches together makes those changes less expensive to someone who depends on the tool as a utility in their work.

Show threadBrian SweetingFeb 4, 2023

@skuwamoto C. I’m in favor of getting new features as soon as they’re ready. It’s never disruptive when a new feature saves me time or effort.

Also, I think there’s a greater perception of progress when large, impactful features are spaced out.

Show threadHanno ten HoorFeb 4, 2023
@skuwamoto release when they’re ready and still feature the at the conference would be ideal for me
Show threadMarcelFeb 4, 2023
@skuwamoto c! Makes the product feel more alive and actually helps with motivation at work.
Show threadBrad EllisFeb 4, 2023
@skuwamoto I’ve seen a cadence of releasing a complicated feature ahead to help supply content and need at the conf, mixed with more consumer releases day of or as faster followers.
So, like, changes in how you build a corporate design system, early. New prototyping features, at the conf.
Show threadGui SchmittFeb 5, 2023
@skuwamoto b) I like both because it's something excited to look forward to and it becomes a ritual within design teams to check it out / connect annually
Show threadjedmundFeb 5, 2023

@skuwamoto much rather c. the way yall do it is fine—i've never been like "wow i hate that they do this"—but i generally prefer a la carte releases than one big one.

with software in general, when a company does big bundled release events, it feels like big stageworthy things get held when they could be making a difference sooner.

Show threadpodoFeb 5, 2023
@skuwamoto C – frequent updates means easier learning curve (you don’t do it once/twice a year, but all the time) and less work for design system kit building (combined changes usually means breaking changes and a lot of rework)
Show threadJustin MaxwellFeb 5, 2023
@skuwamoto c. It’s not 2004 and there’s no Macworld anymore. Users shouldn’t have to wait so founders can publicly congratulate themselves for a thing that was finished months ago. And in those months the team could be getting feedback on it.
Show threadEwoud SurmontFeb 5, 2023
@skuwamoto For the Design System managers among us, knowing when the major changes are going to be released gives me some peace of mind. So for me it’s about it being less disruptive.
Show threadEdFeb 5, 2023
@skuwamoto I don’t as much should be held back for Config as is right now. Some it’s useful to have a lead time so orgs can plan, but the sooner the better for everything else.
Show threadWill ClarkFeb 5, 2023
@skuwamoto c
Show threadRichard EarneyFeb 5, 2023
@skuwamoto I’d prefer smaller, more regular releases. It allows time to digest them and then incorporate them.
You could still have a Config that announces key features but they might come when they are ready
Show threadRichard BruskowskiFeb 7, 2023
@skuwamoto c). New features I am waiting for eagerly, I’d rather get sooner than later. Even if they are somewhat incomplete or in a beta state and the teams I am working in decide to withhold from adapting them right away, I can at least try them, anticipate what is to come, update mental models and opinions. And features that seem more tangential to my day to day work, I can just ignore until they get some stage time at Config or Schema.
Show threadRichard BruskowskiFeb 7, 2023
@skuwamoto Also, a simple changelog note can spark just as much or even more excitement than a big reveal if it is a feature I was looking forward to.
Show threadjuliusloeweFeb 8, 2023
@skuwamoto I’m going with bad here. But the reason is not because it’s not fun but because Figma can react quicker to requests that bag users. Mindblow shortcuts or else
Show threadChrisFeb 8, 2023
@skuwamoto c! It feels better to focus on one thing at a time than to have a stack of features and not know where to start. Also makes it feel more vivid.