Archives before June 13, 2001
Path (my company!)
Most of the Time
American history around the time of the Revolution, figuring out how to marry top-down task-based information architecture processes with bottom-up document-based ones, finding a good dentist in
San Francisco Oakland
the user experience (interaction design, information architecture, user
research, etc.), cognitive science, ice cream, films and film theory,
girls, commuter bicycling, coffee, travel, theoretical physics for laypeople,
single malt scotch, fresh salmon nigiri, hanging out, comics formalism,
applied complexity theory, Krispy Kreme donuts.
to see where I wander.
me you love me by
Track updates of
this page with Spyonit. Clickee
[Editor's note: peterme.com
began as a site of self-published essays, a la Stating
The Obvious. This evolved (or devolved) towards link lists and shorter
thoughtpieces. These essays are getting a tad old, but have some good
Design Recommended Reading List
"My" Is It Anyway?
Information Vs. Application
All contents of peterme.com are © 1998 - 2002 Peter Merholz.
|If I were to build a software product. Posted on 08/05/2002.
It would either be some type of social network communicator, or:
CMS for Intranets -- It seems that so much energy has been focused on supporting the design of external sites, that the operations' needs have gone unsupported. I've been designing Adaptive Path's intranet, and it's surprising how complex the needs of a 7-person company can be. The heart of it is a faceted document repository. I'd be interested in designing a CMS that combines the ease of use of MovableType with the faceted goodness of FacetMap, and allows for an easy building of tools to access a content, project, contact, and user database.
In talking with Marcus about this today, he commented on how the needs of a 7-person company are pretty much as complex as the needs of a 200-person company. Which is probably true--there's just this baseline of rather significant complexity, but it scales remarkably well.
I wonder if there's a significant enough market for such things. Or if it could be built with a platform generic enough to be tailored to these needs, yet not so generic that people wouldn't have a clue what to make of it.
2 comments so far. Add a comment.
Previous entry: "The Interconnectedness of Corporate Malfeasance."
Next entry: "It's in the refrigerator."
Now careful...don't get seduced by the idea that "we could build a generic solution". Think of all those dead software companies that promised (cough..vignette) generic, scalable solutions to impossibly complex idiosyncratic problems.
Posted by Andrew @ 08/06/2002 12:37 AM PST [link to this comment]
I have had this same thought quite often with regard to my (enormous) company. There would be alot of benefit in an internal CMS but there would need to be a ton of upfront design and set up. I think that the biggest hurdle would be getting people to actually use it, that seems to be the problem with nearly every collaborative tool we use around here.
Posted by jonah @ 08/07/2002 05:00 PM PST [link to this comment]
Add A New Comment: