Russ (@rhops) header
Russ (@rhops) profile picture

People Listener, Trend Watcher, Customer Experience, Digital Product Design, CCXP

Grand Rapids, MI
Joined January 2007
Photo by Russ (@rhops)Photo by Russ (@rhops)Photo by Russ (@rhops)Photo by Russ (@rhops)Photo by Russ (@rhops)Photo by Russ (@rhops)Photo by Russ (@rhops)Photo by Russ (@rhops)Photo by Russ (@rhops)Photo by Russ (@rhops)
Russ retweeted
AI has collapsed the cost of building products, but not the cost of knowing what to build. - The old loop: spec, scope, build - The new loop: build, play, design, ship Prototypes are cheap. Great products still require taste, judgment, and a clear understanding of what users actually need. a16z's @joshelman on the artifact a product manager actually produces: a16z.news/p/product-manageme…
150
474
101
3,542
453,246
My biggest takeaways from @Netflix's Chief Product and Technology Officer Elizabeth Stone: 1. Elizabeth believes that “systems thinking” is becoming the most important skill in the AI era. In engineering and product, this means people who can see across business domains and build the common capabilities that let many teams move quickly. In design, it means experience designers who create templates and design systems so that non-designers can ship work that stays coherent and on-brand. The underlying driver is velocity: when more people are doing more types of work at higher speed, you need to be good at building common scaffolding. 2. Systems thinking is learnable: zoom out one level from your specific problem. Given a task, step back one click—what bigger problem does this serve the business, will it scale across the product surface areas, should it become a platform capability? The companion habit: do your job in a way that helps your manager do theirs. This will force you to think about how all the pieces fit together. 3. Expect a storming phase before a forming phase. The role confusion people feel right now (“What is my job anymore?”) is the predictable middle of any transformative technology. Elizabeth’s advice: focus on high-quality source-of-truth data, guardrails on what ships, and constant internal reinforcement that humans own what they create. 4. The top AI labs converged on Netflix’s culture. High agency, high talent density, top-of-market pay, bottom-up thinking, fast experiments—the traits Lenny hears constantly from AI labs were in Netflix’s early culture deck. Elizabeth’s explanation: excellence comes from hiring exceptional people, trusting them to do great work, and holding them accountable. 5. Netflix’s culture is centered around building “excellence as an operating system.” High talent density, radical transparency, context not control, and the keeper’s test. These work together to create an environment of trust and accountability, without bureaucracy. But it’s also uncomfortable. It requires tolerating people making decisions you’d make differently, resisting the reflex to add process when things go wrong, and letting people carry the weight of their own choices. Elizabeth describes the hardest part as “being comfortable in that discomfort.” 6. The keeper’s test is as much about recognizing great people as it is about removing the wrong ones. The test—“If this person told me they were leaving, would I fight to keep them?”—is often cited in its difficult form: the moment you realize someone isn’t the right fit. But Elizabeth uses it predominantly as an entry point for honest performance conversations that are deeply positive. Most of the time the answer is “I would fight so hard to keep you,” which creates the opening to articulate strengths, discuss impact, and name what’s working. Good feedback hygiene needs a forcing function; the keeper’s test provides one. 7. Specialization is trending down—adaptable generalists are trending up. We’re shifting away from narrow stack-layer specialists (pure frontend, pure backend) toward people who can navigate fluidly across layers. The same logic applies to business domain knowledge: the mindset of “I’m a payments expert, full stop” is less valuable than “I know payments well enough and I’m willing to imagine what the future version of this looks like.” The meta-skill is learning to learn, not locking into a single lane. 8. Netflix’s approach to AI fluency is a universal principle, not a level-specific expectation. Rather than rewriting career ladders to specify what AI competence looks like at each level, Netflix added a single aspiration across all roles and levels: AI fluency. What fluency means varies by function and seniority, but the non-negotiable minimum is the same everywhere—an open-minded, experimental mindset, genuine curiosity, and comfort with ambiguity.
80
321
60
2,603
627,194
Russ retweeted
Anthropic: “Fable is an agentic coding superweapon, capable of developing cyber- and bio-weapons at unprecedented speed and scale. We cannot in good faith release it without guardrails.” China: “lmao here’s Fable but open-source. Good fkn luck”
Introducing Kimi K3: Open Frontier Intelligence 🔹 2.8 Trillion Parameters, 1 Million Context, Native Multimodal 🔹 Kimi Delta Attention enables up to 6.3x faster decoding in million-token contexts 🔹 Attention Residuals deliver ~25% higher training efficiency at <2% additional cost 🔹 Built for long-horizon agentic coding and self-evolving workflows Kimi K3 is now live on on Kimi.com, Kimi Work, Kimi Code, and the Kimi API. Open Weights by July 27, 2026. 🔗 API: platform.kimi.ai 🔗 Tech blog: kimi.com/blog/kimi-k3
154
1,018
76
13,828
1,425,187
CONFIG QS: What I’m curious to learn at #config 2026 as I don my fav CoreAI hoodie headed there: 1. Is design becoming more about the automated, hill-climbing loop** instead of the generated artifact? 2. Are words like “evals” and “trajectories” becoming more mainstream than “prompts”? 3. Could the “Kai’s Power Tools” moment be upon us with OSS Impeccable in gh.io/app now? nitter.cf/github/status/20691210… HT @pbakaus @illscience 4. In an agentic world, will the /create-canvas** matter more because spatial thinking is a needed partner to chat? What kind of questions do you hope will get answered there? I will look for the answers (or more related questions) while there … —JM — **OpenEnv as the way commandline.microsoft.com/op… HT @t2govind **/create-canvas slash command in gh.io/app docs.github.com/en/copilot/h…
.@impeccable_ai earned its way to 40k+ stars on GitHub by delivering exceptional value. Today, we are making design and quality a built-in layer for all creators: Impeccable is now a built-in skill in the GitHub Copilot app. AI raised the floor. We’re here to help raise the ceiling.
3
13
2,361
Russ retweeted
Everything we announced at Config, all in the canvas → Figma Motion → Code Layers → Weave tools → Generative plugins → Shader effects and fills nitter.cf/figma/status/206986122…
47
191
70
1,413
206,523
Russ retweeted
FIGMA MOTION IS HERE FIGMA MOTION IS HERE FIGMA MOTION IS HERE Live from Config 2026
846
2,832
2,534
23,675
6,737,167
Russ retweeted
Create the shader and visual effects of your dreams in Figma Live from Config 2026
16
198
87
2,144
304,182
Russ retweeted
Generative plugins, built by you and the Figma agent Describe the tool you need: behaviors, controls, parameters and get exactly what you want for your workflow Live from Config 2026
32
153
59
1,685
273,868
Russ retweeted
Elon Musk explains his 5-step algorithm for solving any problem: "The most common mistake of smart engineers is to optimize a thing that should not exist." "I have this very basic first principles algorithm that I run as a mantra." Elon breaks it down: Step 1: Question the requirements. "Make the requirements less dumb. The requirements are always dumb to some degree, no matter how smart the person who gave you those requirements. You have to start there, because otherwise you could get the perfect answer to the wrong question." Step 2: Try to delete it. "Try to delete the part or the process step entirely. If you're not forced to put back at least 10% of what you delete, you're not deleting enough. Most people feel like they've succeeded if they haven't been forced to put things back in. But actually they haven't, they've been overly conservative and left things in that shouldn't be there." Step 3: Optimize or simplify. "The most common mistake of smart engineers is to optimize a thing that should not exist. So you don't optimize until after you've tried to delete." Step 4: Speed it up. "Any given thing can be done faster than you think. But you shouldn't speed things up until you've tried to delete it and optimize it otherwise, you're speeding up something that shouldn't exist." Step 5: Automate. "And then the fifth thing is to automate it." Elon explains why the order matters: "I've gone backwards so many times where I've automated something, sped it up, simplified it, and then deleted it. I got tired of doing that. So that's why I have this mantra."
100
1,215
61
5,968
1,130,111
Russ retweeted
Code-first prototypes are fast to build. Getting feedback on them is not. A design lead can't leave a comment on one specific state. An engineer can't see the full flow at a glance. The thing that makes a prototype great for building makes it awkward for aligning. So @amylimabean and I built a skill for that (well, mostly Amy). It takes a live localhost prototype and brings it into Figma. Each flow broken out into its own frame, built from your design system components, annotated with the interaction and implementation details. Now the canvas is where you review and align. We refined it live in the video too! My favorite part is a habit I like to lean on: make the agent take one more round trip to validate its own work before it claims it's done. AI sometimes has the tendency to confidently tell you the job's finished when it isn't. Thanks to Amy and the whole @figma crew for allowing me to be a part of this!
5
10
3
170
13,670
A thread of @figma agent prompt examples / screen recordings I helped bring to life to get you started on automations (with 🎵 made on my OP-XY): 🧵 1.) Explore design directions Prompt: Give me 3 style options for this design, one that's organic, one modern, and one retro.
20
66
11
582
83,072
Designers, this Airbnb Design System might be the best ever created in 2025 ✨ Absolutely Sleek 🔥
48
168
10
2,556
102,487
Russ retweeted
Happy Schema by Figma day. A recap of our announcements (roll out dates may vary) → Extended Collections → Slots → Check Designs → And a ton more
33
193
117
1,530
759,178
This 67 page AI report on how 300 execs at software startups like Cursor, ElevenLabs, Sierra (revenue $10m-$1b+) use AI just dropped. I read it all so you don't have to. Top 7 takeaways: OpenAI is still the #1 model provider in the enterprise, but Claude is second. 1/10
47
303
22
2,544
630,170
Russ retweeted
Did you catch them all? Here’s everything we announced at #Config2025 → Figma Sites → CMS in Figma Sites (coming soon) → Grid → Figma Make → Figma Draw → Figma Buzz
180
1,087
621
7,300
7,142,997
Russ retweeted
What is your favorite name for an AI concierge that would assist you in finding events and booking tickets?
0%Letsgo.events
0%Aiconcierge.world
100%Yourconcierge.co
0%Conserg.io
3 votes • Final results
1
104
Airbnb on how to design a winning 10-star product (genius playbook).
14
119
2
1,458
184,349