laugri (@laugrima) header
laugri (@laugrima) profile picture

laugri

@laugrima

📌 Tweets about design, product management and learning

 Lisbon, Portugal
laugri.com
Joined March 2012
  • Tweets1.1K
  • Following210
  • Followers300
54Media
Photo by laugri (@laugrima)Photo by laugri (@laugrima)Photo by laugri (@laugrima)Photo by laugri (@laugrima)Photo by laugri (@laugrima)Photo by laugri (@laugrima)Photo by laugri (@laugrima)Photo by laugri (@laugrima)Photo by laugri (@laugrima)Photo by laugri (@laugrima)
You can’t make a solution that is better than your understanding of the current user experience.
I need to make it perfect! No, you need to do this:
Image from Janis Ozolins (@OzolinsJanis)
17
142
14
989
90,769
The Expert Approach The client has identified the problem and brings in an expert to solve it for them. The Doctor-Patient Approach The client has identified a symptom and brings in an expert to identify the problem and propose a course of action.
2
4
1
38
7,376
Professor Kevin Anderson is addressing all of us in very clear words: »We are heading towards 3 to 4°C of warming across this century, an absolute climate catastrophe for all species incl our own. And all we are doing so far is giving rhetoric and optimism and greenwash.« 🧵1/8
569
5,895
749
11,146
2,750,340
Whichever way you slice it, "clean" handoffs between stages of the software development process create friction and leave each role frustrated due to lack of influence into neighboring spaces. The solution is working in parallel, not expanding your "slice" until burnout. 1/
Diagram showing 6 rough stages of software development: business strategy, user research, UX, UI, front end, and back end engineering. There are four columns with stacked roles and red lines between the roles signifying friction. The first column has product manager, UX/UI designer, and full stack dev roles. The second one has PM, UX designer, UI engineer, and back end dev. The third one has many roles side by side rather than stacked, showing that they work together and there's no "true" handoff. The fourth column just has "unicorn"; it is crossed out.

ALT Diagram showing 6 rough stages of software development: business strategy, user research, UX, UI, front end, and back end engineering. There are four columns with stacked roles and red lines between the roles signifying friction. The first column has product manager, UX/UI designer, and full stack dev roles. The second one has PM, UX designer, UI engineer, and back end dev. The third one has many roles side by side rather than stacked, showing that they work together and there's no "true" handoff. The fourth column just has "unicorn"; it is crossed out.

11
51
12
286
Replying to @Pretotyping
@Pretotyping Hi Alberto. I've applied the pretotyping approach on two projects over the last month. It's great and I loved the book. One question though: how do you think pretotyping and user research should be combined ? For example (next tweet):
1
117
Let's imagine that I just came up with an idea, like "instant feedback on your golf swing via video". Should I first go talk to some golfers and coaches, ask probing questions, ala The Mom Test from @robfitz? Or should I jump quickly into market validation? Both at the same time?
2
156
I stumbled on some amazing stuff from Deep Yellow today deepyellow.net/
Image from laugri (@laugrima)
Image from laugri (@laugrima)
1
117
As an exercise, I reproduced two items from their Shape series on Figma.
Image from laugri (@laugrima)
Image from laugri (@laugrima)
1
75
Made another one
Image from laugri (@laugrima)
54
I just don't get how flying multiple times a year is still seen as acceptable behavior in this climate crisis.
93
Replying to @mozza_studio
@mozzaio hackathon this week-end in sunny 🇵🇹 Caparica with @micka_design @williamhzo @mathieugrac @laugrima. working on an open-source product toolkit embeddable in any SaaS. think Google Meet + Figma natively in the UI, to discuss with your users. liveroom.app
1
4
10
583
The redesign of @Teamkoober I worked on got featured in the @AppStore today 👏
Image from laugri (@laugrima)
Image from laugri (@laugrima)
1
2
150
The latest version of @Teamkoober 's home page. I spent some time on the buttons. I wanted to bring more interesting forms into the design. Higher res image: dribbble.com/shots/21032827-…
Image from laugri (@laugrima)
77
🧵 Anyone can produce design artefacts, but the bar for good design is high. What makes the difference between an amateur and a professional? I came up with 5 tenets for better design: Intention, Deep understanding of the situation, Technical mastery, Feedback loop, and Time.
1
1
2
210
more replies
5) TIME. If I don’t spend time on the thing, chances are I will only scratch the surface. Things worth doing often take time. A better unit than time might be the quantity of thought poured into the project. xitter.cf/Ugo_alves/status/11874…
hugo alves (@Ugo_alves) profile picturehugo alves
@Ugo_alves24 Oct 2019
I saw a guy managing a product today. No Agile. No lean. No frameworks. He just sat there. Thinking hard about stuff. Like a Psychopath.
1
1
1
175
Time also allows for more iterations. The feedback loop must usually be ran several times to arrive to a satisfactory place. The 4 previous tenets take time to learn and execute, but save you back enormous amounts of time later. Start slow to go fast.
40
Load more