Russ

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

[Russ @rhops]

Big update for the best personal relationship management app.

[a16z @a16z]

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: https://t.co/neVI1kyCYY

[Russ @rhops]

Stop letting valuable relationships slip through the cracks. It's live on the App Store today. Let me know what you think! https://t.co/nzDT8KUyuW

[Russ @rhops]

80% of your future revenue will come from your existing network. Yet, most founders do relationship-building the old school way - relying mostly on their own memory or your phone contacts. You are losing money doing it this way. 1/4

[Russ @rhops]

That is why I built Kindred Memory. It is an AI personal CRM. You record a voice note after an interaction, and the AI extracts the context and schedules your follow-up.

[Russ @rhops]

I realized I was dropping the ball on great connections because I simply forgot to follow up, forgot names or forgot details of our conversation. Traditional CRMs felt like data-entry jobs and are not light weight enough . I needed something that worked for me and reduced manual effort.

[Lenny Rachitsky @lennysan]

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.

[Alaric @0xAlaric]

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”

[Russ @rhops]

Saw this SNL skit and thought of the conversation between @jpatel41 and @zoink at #config https://t.co/zT2utja7KX

[Russ @rhops]

"Demo before the memo" show me the thing, help me play with it, explain the why behind the design decisions.
#config #configLC

[Russ @rhops]

Atlassian agent design principles:
-dont take people out of their flow
-retain accountability
-make user decisions contextual to where they are
-transparency around what an agent has done, but not overwhelming a broader team with all the steps
-permissions are critical
-content should be malleable - text can be visual, video can be static. Should not always be a wall of text
#config

[Russ @rhops]

Design systems become super important when designing with agents. Agents need to understand the intent behind the component, what we see as good design for example how to construct a page, how to pair colors, etc. Then encode it as a skill. #config #configLC

[Russ @rhops]

How do you learn about agent experience? Expedia has 9-10 agents in development for different use cases, learning about how users are interacting.
-Launch with optimism.
-Create moments of transparency and ask for forgiveness as you are learning and testing #config

[Russ @rhops]

When is it ok to break a flow? Lean into places that users are curious and the pain points are obvious.
#config

[Russ @rhops]

Designing for agents:
How do you balance the familiar with the new? Keep user mental models intact especially around critical user flows.
#config #configLC

[Russ @rhops]

Insights from Designing workflows of the future
- eval testing is the future of design qa: give guardrails for the type of output you want
- Last 20% of a design takes way longer than first 80% that you get from a one shot prompt - this is where expertise comes in
- Magic happens at the intersections between types of expertise
- Specialization allows you to not think about constraints for a second which sometimes helps solve a problem
#config #configLC

[Russ @rhops]

How to level up design leader contribution
- change and growth need to be designed
- be a cartographer for your business
- put research upstream to understand product adoption
- billboard to button - end to end experience crits
- Shared primitives - define what is a feature? What is a product?
- Kill your darlings
- bring design into leadership
- design makes change legible
#config #configLC

[Russ @rhops]

Depth of understanding of customers is the future differentiator. #config

[Russ @rhops]

Within OpenAI, adoption of new tools would go from 20% of power users to 80% of team with just one human to human session explaining it. #config #configLC

[Russ @rhops]

Used to be that you could justify design spend by the fact that discovering issues and making changes in code was the most expensive way change a product. Now code is almost free, so design leaders need to rethink this equation. #config #configLC