Doodling

RT @tldraw: Thank you to everyone who's filled out our user survey so far!. If you haven't done it yet, there's still some time left. This….

🔈 I joined the Complementary Podcast to deep-dive on Conceptual Modelling, one of the critical Elements of Product Design (IMHO). Thanks for having me @KatieLangerman and @hobdaydesign!.

People replying “this is dope” … 🤦‍♂️ . It’s nonsensical!. Just think for a second: what is the use case here? To see a clock changing its time when I scroll? And also what music is playing? 😭 Come on. I’m all for experimentation, but the responses really puzzle me.

Depressing, but some good prompts in here for managing the perception of your work. If you're in the weeds, or appear pessimistic and uncertain, your impact will be judged as low. Also see the book Stealing the Corner Office for why working hard unfortunately doesn't pay off.

I love @tldraw but is there a way to turn the novelty snowstorm off?

You can learn all this by being really tightly integrated with a high-performing engineering team. Instead it's quite common to see designers leaving all the stuff above to the engineers. And then wonder why their precious design is twisted and compromised by that other team.

It's also just. hard for designers to engage with some of this stuff if they focus their energy on Figma only.

I think the reason is that developers are forced to think about all this stuff in the process of making it REAL. But these are all design decisions and ideally a product/UX designer should engage just as much with them as an engineer.

14. Conceptual and data models - the relationship and cardinality of objects which has a massive effect on the interactions and layout.

10. Moving forward without breaking changes; migrating information from old features to new. 11. Stress-testing a design with edge cases . 12. How a design will respond to screen sizes, text sizes, translations, accessibility. 13. Modularisation and reusability of UI.

7. Consistency boundaries - where data should agree with itself and where it can become eventually consistent instead. 8. Capturing intent (eg commands) instead of mutating state. 9. Strategies to slice a design thin and release incrementally.

3. The power of pairing on a problem. 4. The power of example-driven design - working with real scenarios and data. 5. The feedback and ideas you get from testing in the real medium (real code in browser not Figma). 6. Considering how to make tools safe from destroying data.

Many designers are 10 steps behind engineers in the discipline of shaping and shipping software. Things many designers are yet to internalise, that would multiply their impact:. 1. Small batch size to reduce risk and speed feedback . 2. Walking skeletons to flush out obstacles.

When advocating for a faster UI it’s helpful to have a semi-objective measure in mind. Ask “which of these limits do we need to hit?” Instead of just complaining it’s too slow.

Be careful marketing yourself as “self-taught”. Firstly, it’s never true: we all learn from outside sources — peers, books, conferences, videos, short courses. Secondly, it doesn’t sound like a selling point — it implies you’ve missed valuable external perspective.

RT @tom_d_kerwin: [Please share] Calling all people who work in tech! 🙋 . Got 10 minutes to try something different? . Along with @johncutl….

Are you looking to create a lightweight research repository, but not ready for something like Dovetail?. Try my Notion template, available on @Gumroad

Any other designers still refusing to say UX and UI?. I’m here still saying Interaction Design and Visual design. I’m not alone…. Am I?.

I’m signed up to do a talk at @UXCampBrighton #uxcb

(Found in my spam folder).