whimsy
emojraw.glitch.me (draw!)
A Website by Shannon LinSpreadsheet Portfolios for UX Designers
An Article by Erica HeinzThe “case study?” column was the whole point of the spreadsheet — identifying which projects I still needed to write up for my portfolio — but at this point I looked at the sheet, and thought “This is honestly a better overview of the work I do than any ‘portfolio’ I’ve seen”.
So I tweeted a screenshot, joking/trolling that it WAS my portfolio (I didn’t include any winks or notes that I was still planning a “real” portfolio), but people didn’t respond with the lulz I expected — they got the idea, or took it at face value and said they were going to do their portfolio this way too!
A small store
A Gallery by Kyeoung Me LeeExit pages
An Idea by Brad EnslenToday I made an Exit page. So many people end their visit by hitting the Back button on their browser. The exit page is a last attempt to get them to explore the Blog Directory to find an entertaining blog. Or failing that to try a search on a search engine they may have never tried before.
The Whimsical Web
A Website by Max BöckA curated list of sites with an extra bit of fun.
Funcooker
A Websitemultiverse.plus
A Website by Kicks Condor & Weiwei HsuAn audacious attempt to reshape blogging, to see where it can go next!
Podcasts and video have really taken over - to the extent that it feels like reading may be falling behind. Can we enhance text and imagery on the Web? Try to give blogging new life?
Lizzo's Juice Shop
A Websitelittlebigdetails
A Blog by Floris DekkerLittle Big Details is a curated collection of the finer details of design.
As Charles & Ray Eames put it:
“The details are not the details; they make the product.”
This is intended to be a source of inspiration.
Created and curated by Floris Dekker. Alumni: Andrew McCarthy.
Games For Crows: Feels
A Game
Software that nobody wants
Finding value is the result of enabling individual and group-level discovery attempts. It's not the result of everyone following one leader's gut.
What just happened is a new software product/feature was created that no customer wanted. This happens way too often. In fact, most hyper important software projects that must be done by date certain or else, have deep flaws that cause some variation of this phenomenon, flaws that include:
- Not wanted - Company specified a solution to a problem that customers don't actually have
- No Rarity - Company is pursuing an iKnockoff of existing products. The market already has two scaled competitors with working solutions, customers naturally spend budget on products that are already successful to avoid risk
- Incorrect Packaging - Customers need a website, but the company created an iOS app instead
- Incorrect Pricing - Customers need SaaS pricing, but the company created a shrink wrapped, on-premise solution with CapEx and maintenance agreements instead
The 'date scrum' anti-pattern
Date Scrum is an R&D pattern where developers are asked to estimate software project requirements upfront for the entirety of the project. After the project is green lighted and the budget is set based on the final estimates, the team then holds daily scrums to status and manage risk as they “iterate” the solution toward the release date. To some, this approach is described as doing Waterfall in sprints.
The fundamental problem with Date Scrum is that the team is de-focused from discovering the best solution. Instead they are heavily focused on delivering Something™ by the Date™. Engineers are problem solvers, and if the primary problem becomes delivering Something™ that will pass QA by the Date™, they will, with enough pressure, solve that exact problem.