Matt Baxter ⚡️ (@mbxtr) header
Matt Baxter ⚡️ (@mbxtr) profile picture

Tweeting about product management, design, tech, coffee, and whatever else · Interneting at https://xitter.gq/t.co/upyGJBRTA1

Dallas, TX
Joined March 2007
Photo by Matt Baxter ⚡️ (@mbxtr)Photo by Matt Baxter ⚡️ (@mbxtr)Photo by Matt Baxter ⚡️ (@mbxtr)Photo by Matt Baxter ⚡️ (@mbxtr)Photo by Matt Baxter ⚡️ (@mbxtr)Photo by Matt Baxter ⚡️ (@mbxtr)Photo by Matt Baxter ⚡️ (@mbxtr)Photo by Matt Baxter ⚡️ (@mbxtr)Photo by Matt Baxter ⚡️ (@mbxtr)Photo by Matt Baxter ⚡️ (@mbxtr)
Matt Baxter ⚡️ retweeted
CLOSED BETA WAVE 3 IS LIVE. The gate is open, and the war continues. Secure access now thecitadel.com/
353
298
16
421
20,314
Matt Baxter ⚡️ retweeted
Introducing Co-Reader: Knowledge on Tap For too long, "AI in reading" has meant 31 flavors of summarization. Today, we're thrilled to introduce a new feature that feels both intuitive and essential. Co-Reader anticipates questions as you read, offering instant answers and deeper context without interrupting your flow. The magic lies in its effortlessness. Tap a paragraph to see questions. Tap a question to see answers. No typing. No switching apps. Just knowledge on tap. Co-Reader is powered by @perplexity_ai and was directly inspired by Perplexity’s "Related Questions" feature. In many ways, using Co-Reader feels like bringing Perplexity into the written page. Try it and let us know what you think.
29
32
18
454
58,843
Matt Baxter ⚡️ retweeted
I’ll admit it: I do something teams might hate. I come over the top with ideas, interrupts, and reprioritization. Why? It’s not because I don’t trust folks or think they are generally working on the right things. It’s to lend authority to agility. What do I mean? The systems needed to run large teams against ambitious outcomes are built to reduce chaos: share context, create predictability, derisk delivery, and ensure quality (of decisions, priority, outputs.) Cultures that defer to these systems—planning, alignment, commitments—open struggle with executing on a few categories of work: - important but not urgent - urgent but not planned - high risk high reward (short or long term big bets) Teams acknowledge these categories of work are important, and so they adapt the system to account for them. Example: setting aside time in sprints or roadmaps for tech debt (important but not urgent) or having tiger teams peel off for moonshot projects (high risk high reward.) But these strategies are often about preserving the system, and narrowly allowing exceptions. And it often just becomes the fact that these systems determine what you work on. These concepts of roadmaps and sprints and okrs and tiger teams and allocation all become constraints that on a quarterly/monthly/weekly/daily basis of what you “should” be doing, and it takes tremendous effort to do something different. It becomes very easy to predict what will be built, but very difficult to change it. In a world where predictability reigns supreme, being wrong is perceived as expensive. PMs are putting their names on priorities, engineers are assigning themselves story points, and you can start to operate as if “I did what I said I would” is the end all/be all to success. But we all know that’s not true. The key to success is building things that matter (to users, to customers, to the business.) And sometimes insights about what matters comes fast and furious—a user says something during research, you sign a big new exciting customer, some new tech (hi gen ai) fundamentally changes things. And this is where advice to rising directors, VPs, etc. go sideways. The prevailing wisdom/discourse is more systems, frameworks, etc. to preserve predictability, and the promise is those frameworks will output the right outcomes. And leaders get in this weird role of acting as a shield between the variances of the business (high!) and the ops of the team. But sometimes permission, not protection, is the best thing you can offer the team as a leader. Permission to say you were wrong and something else is more important. Permission to ask for a different deadline. Permission to call a time out. Permission to not have everything planned out for quarters. Permission to disagree with a design. Permission to break org lines when staffing projects. Permission to pluck from someone else’s backlog. Permission to have a reasoned guess, and build it fast. Permission to *feel* the reality of a growing business. It’s really hard to get to the leadership level without knowing the general ways to run a team and product without pure chaos—this isn’t where I see most leaders need development. Instead I’d love to see more people focus on how to develop skills around instinct, craft/taste, scoping, rapid change management, and independently holding decisions (vs aligning orgs around them.) Leaders are the very few in the org with the authority to quickly change course, and maybe we should start looking at that as a feature, not a bug.
19
30
10
369
93,556
Matt Baxter ⚡️ retweeted
Prepared to get absolutely roasted here, but it’s a very clear observation I see people afraid to articulate. If you want to be a very top performer, you have to be - smart - fast - available - adaptable - low ego Pick no less than 5.
13
5
2
93
11,661
Matt Baxter ⚡️ retweeted
Read about punch cards, plotters, light pens, kinetic machines and heaps more in my new article about Early Computer Art in the 50's & 60's! amygoodchild.com/blog/comput…
16
111
20
351
36,069
Matt Baxter ⚡️ retweeted
Wordle guess your tax refund
16
141
10
3,966
300,674
Matt Baxter ⚡️ retweeted
Say Hello to Ivory. Our Mastodon client for iOS available on the App Store! If you liked Tweetbot, you'll love Ivory and feel right at home. Go download it, try it free for 7 days, and experience it for yourself! apps.apple.com/us/app/ivory-…
91
833
243
1,769
754,058
Matt Baxter ⚡️ retweeted
Say Goodbye to Tweetbot. We've been proud to serve you over the last 12+ years, but due to circumstances beyond our control, we have to shut down Tweetbot. Thank you so much for your patience and outpouring of support over these tough times at Tapbots. tapbots.com/tweetbot/
910
3,925
2,636
13,369
4,677,746
Matt Baxter ⚡️ retweeted
Definitely felt this today. Great post about the reentry to work by @aworkinglibrary: “You’ve been in orbit, and now the friction of the atmosphere is rapidly warming you up, and weight is coming back into your bones, and it’s a lot to feel all at once.” aworkinglibrary.com/writing/…
3
4
877
Matt Baxter ⚡️ retweeted
Yo I heard you like Raycast swags — so here's a Christmas giveaway 🎅 I'm giving a mug and stickers to one random person* who retweets this tweet ❤️ * who's following me (@peduarte) and @raycastapp
43
248
27
311
82,095
Matt Baxter ⚡️ retweeted
It’s official! Bestow closed on our acquisition of Centurion Life Insurance Company, an insurer with a national reach. Read more about the news via @DCEOmagazine. https://xitter.gq/t.co/LlGrSe21WM
1
4
America is remarkable because of our ability to recognize the failures of the past while dedicating ourselves to building a better future. #Juneteenth
178
1,114
102
5,006
Matt Baxter ⚡️ retweeted
There are Good Product Managers and there are Great Product Managers. There are also Okay Product Managers and Bad Product Managers, but we will focus on the Good and the Great here. Good Product Managers, Great Product Managers, a thread:
184
1,446
353
6,754
Matt Baxter ⚡️ retweeted
RAMS IS STREAMING FREE NOW. My film about designer Dieter Rams is free to watch this week, go to: ohyouprettythings.com/free As the COVID-19 crisis continues, I'm streaming my design films free for viewers staying indoors worldwide. Hope you enjoy, and stay safe.
9
170
56
399
Matt Baxter ⚡️ retweeted
3 types of gaps between plans and reality: 1) Information gap - we always plan with incomplete information 2) Alignment gap - execution doesn't accurately follow the plan 3) Effects gap - Our actions don't always generate the expected outcomes. (source: Stephen Bungay)
2
10
Most roadmaps are setting up their product teams to fail. That's because, even today, most roadmaps still follow the dreaded *timeline roadmap* format 😱 And here's why that sucks. THREAD 👇
139
1,926
519
6,186
Matt Baxter ⚡️ retweeted
I just posted an article that I fully expect will upset many in the product community, but I believe it's important, and I'm hopeful it can explain most of the noise and confusion in the community about the role of product: svpg.com/product-vs-feature-…
42
312
123
801
Matt Baxter ⚡️ retweeted
Startup marketing strategies converge at the top. Selling a database to big companies is very different from getting users for a mobile game, but in both cases there's nothing better than making something so good that users spontaneously recommend it to others.
12
133
8
779
Matt Baxter ⚡️ retweeted
Don’t get customers hooked, focus on healthy retention instead elezea.com/2019/07/hooked-he…
1
5
Matt Baxter ⚡️ retweeted
I’m sure I’m not the first person to suggest this, but I wish “product managers” were called “product stewards” instead. It much more accurately describes the nature of the job.
4
14