The saddest designer An Essay by Chia Amisola chias.blog I am tired of the premise that creation means productivity––especially in the laborious sense...Creation has become mangled with labor in a world that demands man to monetize all of their hobbies and pursuits. In return, it seems empty, almost sad, really––to be the designer spending weekends again on the screen. To tell you what I like to do in the weekends, I like to do the sad thing...The ‘good’ people tell you to detach your life from your workspace, but this summer, I think I’ve just realized how much I adore what I have the luxury of working on everyday. In the weekend, I make. I make not because it’s the only thing I have ever known, but because it’s the most certain way forward. To see the fulfillment of the workYour life adds up makingidentitywork
The web in decay is the web by design An Essay by Chia Amisola chias.blog When will there be a guide to best practices for archiving the web? Will the giants responsible for the platformization of the web make the act of digital archival any easier for us? Is it foolish for platforms like Snapchat or Instagram Stories to brand themselves as “temporary” when temporariness is impossible on our internet? Should the web exist as something organic, malleable, and destructible –– or as an eternal timekeeper? Is link rot more of a technological issue or a human one? Do humans want to know themselves forever? The Internet Is Rotting decaywww
In defense of disorder: on career, creativity, and professionalism An Essay by Chia Amisola chias.blog Professionalism is a lie, build what you love, explore everything. In today’s age of creation, anyone who attempts to tell you otherwise is lying. You’ll end up seeking what you traded for the rest of your life. Successful careers are not planned workcreativitybureaucracy
Product vs. Feature Teams An Article by Marty Cagan svpg.com This article is certain to upset many people. Empowered product teamsViability, usablity, feasibilityWhat went wrong? featuressoftwareagile
Empowered product teams When I wrote about the virtues of empowered product teams, I was referring to what I’ll continue to call here as product teams. Specifically, they are cross-functional (product, design and engineering); they are focused on and measured by outcomes (rather than output); and they are empowered to figure out the best way to solve the problems they’ve been asked to solve.
Viability, usablity, feasibility In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us. However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap. What went wrong? teamwork
What went wrong? If something ships from one of the companies I advise, and it is virtually unusable because of poor design (which as we all know occasionally does happen), you can bet I go directly to the designer and ask how this happened? It is absolutely on the designer to ensure this does not happen, so something went wrong. Similarly, if the product ships and performance is terrible you can bet I go directly to the tech lead with the same question. And most frequently of all, if something ships and the analytics show that it’s either not being bought or not being used, or it turns out that it violates some business constraint like compliance or privacy, you can bet I go right to the product manager with that question. Viability, usablity, feasibility