I'm beyond excited to finally introduce y'all to my new company: Markham Square — a digital product studio dedicated to helping product teams craft exceptional digital experiences.

Have reached the point where I'm building mini custom apps for YouTube videos, let's see how long I can keep this up 😆.

If you're leading a product team, listen to this one. It’ll make your team, and your product, better. 📺 Watch here: .🎙️ Listen here:

Even in the era of AI + vibe coding. Teams that talk well, build well. No amount of tooling replaces human alignment.

The secret weapon is team alignment. Clear ownership. Open communication. Shared goals. Cohesion doesn’t happen by accident, you build it on purpose.

His biggest takeaway? You don’t wait for user research to start empathizing with your users. Every team member, dev, design, PM, should bring their own user lens to the table.

Most product teams obsess over features, the best ones obsess over team cohesion. Just dropped a pod w/Jason Chen from Trestle on what makes great product teams actually work 👇

Full breakdown in the episode:.🎥 If you’ve ever left a product meeting thinking “what just happened?”, this one’s for you.

Specificity isn’t just good communication. It’s an unlock for better collaboration, tighter execution, and stronger products.

Example:.👎 “This isn’t working.”.👍 “This hover-state micro-interaction on the input border needs to animate on delay.”. The difference? Clarity. Speed. Confidence. Better execution.

The framework breaks the product down into 5 levels:. 1. Micro-interaction.2. Feature.3. Feature set.4. Product experience.5. Product ecosystem. Think of it as a shared map for product conversations.

In this week’s Tech Takes, we break down a framework called Product Elevation. It helps teams get radically clear on what part of the product they’re actually discussing.

Too many teams burn hours debating things without realizing…. They’re not even talking about the same thing. A feature? A micro-interaction? The whole experience?. If you’re vague, your team stalls.

An under-appreciated characteristic of the best product teams?. Specificity. Let me explain 🧵.

If you want to build software that sticks, this is one to bookmark. 🎧 Listen: .📺 Watch:

Some gems from the convo:.- Why empathy is a developer’s superpower.- Why every sprint ticket needs a clear “why”.- How getting devs closer to users leads to better iteration.- What happens when you skip user context: tech debt.

Dee started out working in the legal system, not technology. And, what made her great there: context, clarity, and communication, made her an even better developer. The result?. She builds tools users actually want to use.

Great products don’t win because they have the most features. They win because users feel like they were built for them. On the latest Technically Lit, I talked to Salesforce dev Dee Knell about what it really takes to build with empathy especially when you’re not a technical

@boltdotnew Thank you to everyone who's supported us so far - we have so much awesome content planned for Technically Lit, and I’m so excited to share it all with you 🙌 . Join our newsletter here:.. Giveaway ends Monday 6/23 @ 12pm EST.

A small win for some, but super excited that Technically Lit has hit 500 YouTube subscribers!. To celebrate, we're giving away a 1-yr PRO @boltdotnew subscription to a follower!. To enter:.1️⃣ Follow @nickjbasile.2️⃣ Retweet this post.3️⃣ Join our newsletter (link in next post)

The Design Paradox: The more attached you are to your mockups, the harder it can be to ship. Try not to let let pixel perfection cost you progress!. Ep 003 - Start ugly: a product design process that drives results - Tech Takes. __.#productdevelopment #productdesign #startup