Kyle Murphy (@noluckmurphy) header
Kyle Murphy (@noluckmurphy) profile picture

Product, design, research and people leader. Owner: KRM Consulting, LLC. Formerly @Hudl @Buildertrend. Mediocre golfer and sci-fi lover. He/him.

Lincoln, NE
Joined May 2008
I mainline audiobooks at 3x so I have a need for more agent voice speed, and an ability to make the default voice of a new run at that speed because I’ve spent the last 10 minutes updating all my bots to speak faster cc @bot
1
184
Kyle Murphy retweeted
For people new to design jigs, this is a good example of using them in the wild. I first saw them used by @doctorbaytas in this beautiful talk at @meetgranola: youtube.com/watch?v=t57p7ARE…
added a little bit of spice to the bookmark animation, opus 5.5 btw
9
18
1
435
47,476
SVPG #ProductManagement Quote of the Day
1
6
29
Kyle Murphy retweeted
A feature is not 'DONE' until it's had impact! Too many orgs ship a new feature and immediately move on to the next shinny object. And seldomly cycle back to anything they've shipped previously to measure the outcome.
13
45
6
211
28,492
Yesterday, 50 builders attended our first Builderbond event in Omaha. We teamed up with CBUSA to offer this networking opportunity for local builders. Are you interested in an event like this in your area? Let us know in the comments. ⬇️
1
8
643
Kyle Murphy retweeted
Design Research Framework The most important use of this diagram is as a touchstone and a checklist in conversation with anyone who participates in design decisions throughout your organization muledesign.com/blog/design-r…
42
265
19,842
Every ERP implementation I’ve ever seen was underestimated in three ways: 1. The number of people involved 2. The importance of master data 3. The amount of culture and process change required
5
8
1
77
11,912
I know it's rough out there learning Computer Science from scratch, so I translated some of the C++ primitives to something that us zoomers can understand.
114
1,013
149
6,393
584,089
Kyle Murphy retweeted
all the crypto bros who pivoted to AI reading about superconductors rn
139
1,250
142
20,156
1,541,749
Today on “The Building Code,” Zach and Charley welcome Brian Pavlick, president of CBUSA and Buildertrend’s GM of materials management. Listen to the full episode to hear more about the launch of Buildertrend Purchasing: btrnd.co/44ysLc4.
1
6
442
When you’re a product designer and the PM jumps into your Figma file to “sketch something out” but it actually turns out decent.
10
80
7
987
158,662
Courtesy of @datasniff, just discovered the fact that @Twitter profile pages now include a #JSONLD based #KnowledgeGraph. Good move, as #SocialMedia #CageMatch progresses to round 2 😀 #RDF #SemanticWeb #DigitalTwin #LinkedData #Identity #Authenticity #SSI
6
20
1,347
A critical secret to understand is that having real diversity on your team means less social cohesion. What does less social cohesion mean? It means more frustration. It means more arguments. It means less "Sounds great!" and more "No! That's wrong!" 🧵
2
9
3
42
18,680
Here we go, again :) 🔥
28
49
16
536
107,519
#wordnerd 🚨 Reviewing The Accidental Taxonomist w/ Heather Hedden youtu.be/t6YPsCJwYts
1
192
mckinsey innovation strategists were paid seven million dollars to come up with this framework
10
37
3
377
43,328
Producing high-fidelity artifacts before you're certain you are solving the right customer problem:
4
20
1
118
11,043
Kyle Murphy retweeted
Why does @amazon use storyboards as a key part of their #UX design process? @PavelASamsonov – design architect at @awscloud – uses lo-fi storyboards to clarify what problem he’s trying to solve, long before he designs a single screen. 1/3
3
5
1
38
4,129
I'm putting together a list of the most common problems in data/analytics: 1. Numbers don't match / are wrong 2. Can't trust the numbers / data 3. Don't know which numbers / tables / metrics to use 4. Data is messy / wrong 5. Data is inconsistent / changes too often 6. Too many dashboards / tables / metrics 7. Too many ad-hoc / one-off requests for data 8. Many data science projects fail or don't deliver value 9. Low trust in the data team Am I missing something?
23
7
4
95
20,176