







Retrospective on Project Xanadu’s success and failure: a lack of design iteration, meaningful use-cases, or practicality stopped a valuable vision from maturing into something useful. (And contrasted with my approach.)
Project Xanadu
Wired magazine published an article entitled "The Curse of Xanadu", calling Project Xanadu "the longest-running vaporware story in the history of the computer industry".[3] The first attempt at implementation began in 1960, but it was not until 1998 that an incomplete implementation was released. A version described as "a working deliverable", OpenXanadu, was made available in 2014.
The Curse of Xanadu
It was the most radical computer dream of the hacker era. Ted Nelson's Xanadu project was supposed to be the universal, democratic hypertext library that would help human life evolve into an entirely new form.
The lessons of Xanadu
“The longest-running vaporware story in the history of the computer industry”

Project Xanadu®
"Xanadu®" and the Eternal-Flaming-X logo are registered trademarks of Project Xanadu.
An FPM critique: The Gantt Chart and the hidden history behind your project timeline
It's one of the first tools most project managers learn about. Colourful bars stretching across a timeline, tasks lined up neatly, progress tracked against a plan. The Gantt chart feels logical, even neutral. Just a visual way to organise work. But like the RACI matrix, when we look more closely at where this tool comes from and what values it was built on, the picture becomes considerably more complicated.

A Better Memory Bank - Convergence.ninja
As my projects grow and evolve, I've come to realize that a simple snapshot of the "current state" isn't always enough. To truly understand a project's journey—the why behind the what—you need context. You need history. My original Memory Bank was great for telling me where I was, but it wasn't so great at telling me how I got there. That's why I decided it was time for an upgrade.
An introduction to radical participatory design: decolonising participatory design processes
Outside of community-led design projects, most participatory design processes initiated by a company or organisation maintain or even strengthen power imbalances between the design organisation and the community on whose purported behalf they are designing, further increasing the absencing experience. Radical participatory design (RPD) is a radically relational answer to the coloniality inherent in participatory design where the community members’ disappointment is greater due to the greater expectations and presencing potential of a ‘participatory design’ process. We introduce the term RPD to show how research and design processes can be truly participatory to the root or core. Instead of treating participatory design as a method, a way of conducting a method, or a methodology, we introduce RPD as a meta-methodology, a way of doing any methodology. We explicitly describe what participation means and compare and contrast design processes based on the amount of participation, creating a typology of participation. We introduce ‘designer as community member’, ‘community member as designer,’ and ‘community member as facilitator’ models and provide characteristics for the meta-methodology of RPD.

An introduction to radical participatory design: decolonising participatory design processes
Outside of community-led design projects, most participatory design processes initiated by a company or organisation maintain or even strengthen power imbalances between the design organisation and the community on whose purported behalf they are designing, further increasing the absencing experience. Radical participatory design (RPD) is a radically relational answer to the coloniality inherent in participatory design where the community members’ disappointment is greater due to the greater expectations and presencing potential of a ‘participatory design’ process. We introduce the term RPD to show how research and design processes can be truly participatory to the root or core. Instead of treating participatory design as a method, a way of conducting a method, or a methodology, we introduce RPD as a meta-methodology, a way of doing any methodology. We explicitly describe what participation means and compare and contrast design processes based on the amount of participation, creating a typology of participation. We introduce ‘designer as community member’, ‘community member as designer,’ and ‘community member as facilitator’ models and provide characteristics for the meta-methodology of RPD.


Jenny Wen: The design process is dead. Why Designers can no longer trust it.
Designs for the pluriverse: radical interdependence, autonomy, and the making of worlds
"Arturo Escobar presents a new vision of design theory by arguing for the creation of what he calls 'autonomous design'--a design practice aimed at channeling design's world-making capacity toward ways of being and doing that are deeply attuned to justice and the Earth"--Publisher description

Abdelrahman's playground
designer building thoughtful little apps and interactions. reverie, nomi, and a metal shader playground.

Tantacrul – Achieving Excellence in Open Source Software Design #FOSSDesign
Design Thinking
In the past, design has most often occurred fairly far downstream in the development process and has focused on making new products aesthetically attractive or enhancing brand perception through smart, evocative advertising. Today, as innovation’s terrain expands to encompass human-centered processes and services as well as products, companies are asking designers to create ideas rather than to simply dress them up. Brown, the CEO and president of the innovation and design firm IDEO, is a leading proponent of design thinking—a method of meeting people’s needs and desires in a technologically feasible and strategically viable way. In this article he offers several intriguing examples of the discipline at work. One involves a collaboration between frontline employees from health care provider Kaiser Permanente and Brown’s firm to reengineer nursing-staff shift changes at four Kaiser hospitals. Close observation of actual shift changes, combined with brainstorming and rapid prototyping, produced new procedures and software that radically streamlined information exchange between shifts. The result was more time for nursing, better-informed patient care, and a happier nursing staff. Another involves the Japanese bicycle components manufacturer Shimano, which worked with IDEO to learn why 90% of American adults don’t ride bikes. The interdisciplinary project team discovered that intimidating retail experiences, the complexity and cost of sophisticated bikes, and the danger of cycling on heavily trafficked roads had overshadowed people’s happy memories of childhood biking. So the team created a brand concept—“Coasting”—to describe a whole new category of biking and developed new in-store retailing strategies, a public relations campaign to identify safe places to cycle, and a reference design to inspire designers at the companies that went on to manufacture Coasting bikes. [hbr_brightcove id=”4443548301001″]

wait a second, it just dawned on me that atproto delivers on most of the project xanadu concepts that don't require a shit ton of lsd to understand?? minus payments which is what sunk xanadu anyway. fun cs lore rabbit hole for the uninitiated! xanadu.net
A great talk from @jenson.org on why and how to move the desktop paradigm forward. I especially loved the prototypes/concepts; even if not perfectly refined it’s still nice to see someone put some stakes in the ground. (And FWIW I think they were all pretty solid!)
Scott Jenson
Thoroughly enjoyed speaking at #UbuntuSummit today. Thank you organizers! I spoke about the need for new foundational #UX improvements to the Desktop UX. Very lively audience! youtube.com/live/WvNgMEumSoA?t=17225s