Kurt Grandis
Chapel Hill, North Carolina, United States
581 followers
500+ connections
Activity
-
A strong reminder from this year’s Owners’ Meeting: when #EmployeeOwners align around a shared mission, real impact follows. Proud to be part of that…
A strong reminder from this year’s Owners’ Meeting: when #EmployeeOwners align around a shared mission, real impact follows. Proud to be part of that…
Liked by Kurt Grandis
-
💸 DjangoCon US 2026 Opportunity Grants are now open — and the deadline is coming up. If the cost of travel or lodging would prevent you from…
💸 DjangoCon US 2026 Opportunity Grants are now open — and the deadline is coming up. If the cost of travel or lodging would prevent you from…
Liked by Kurt Grandis
-
This week in Phoenix, our D&IT leadership team came together to listen, learn, and align. We grounded ourselves in empathy for the clients we serve…
This week in Phoenix, our D&IT leadership team came together to listen, learn, and align. We grounded ourselves in empathy for the clients we serve…
Liked by Kurt Grandis
More activity by Kurt
-
9-months in the making and I fell sick and could not attend in person! Despite the bad luck, I was able to attend our Black & Veatch D&IT Leadership…
9-months in the making and I fell sick and could not attend in person! Despite the bad luck, I was able to attend our Black & Veatch D&IT Leadership…
Liked by Kurt Grandis
-
Recordings of the DjangoCon US 2025 talks are now available to watch back on YouTube. There were too many great talks to list them all but there’s…
Recordings of the DjangoCon US 2025 talks are now available to watch back on YouTube. There were too many great talks to list them all but there’s…
Liked by Kurt Grandis
Explore more posts
-
Paul Chiusano
I thought this was a good and very reasonable talk by Eleanor Millman on how to prioritize projects for a platform engineering team: https://lnkd.in/gaYtUHRH A few insights I took from it: - Unlike product features which can be more directly tied to revenue, platform engineering work is a couple steps removed. But that doesn't mean it's unimportant! Far from it, platform engineering projects can make everyone at the company more efficient, able to produce higher quality software, etc. - While "urgency" is always going to be a factor, you don't want to just be putting out fires, you want be able to prioritize work which is "high impact" ... even if that impact isn't felt immediately. - Good rule of thumb: prioritize "highest impact for lowest effort". - The talk has some ideas on what factors to choose for impact, and how to blend them. For instance "speed of development" is one factor, "cloud cost optimization" might be another. The weighting of different impact factors can change over time, depending on the needs of the business. I would say that a lot of companies don't have much methodology here but I can really see the value in codifying it. You can always change the methodology or the weighting if it's spitting out results that don't pass the smell test or you really feel it is leading the company astray. Clarity can give the org more freedom to put resources behind projects that would otherwise never be taken on. When things are unclear, prioritization still happens implicitly, but the decisions tend to be a lot more random and fear-based and the org is worse off as a result.
3 Comments
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content