A Work In Progress
History is nothing more than a vast collection of todays.
Click to see the XML version of this web page.

Subscribe to "A Work In Progress" in Radio UserLand.

Click here to send an email to the editor of this weblog.


Monday, January 21, 2002


Either these rules apply to much more than just entrepeneurs, or I'm much more entrepeneurial than I thought. From Dave Sifry: Rules for Entrepeneurs 

comments   permalink 




As I review project proposals, replete with sections entitled "Risk Assessment," "Solution Overview," "Deliverables," and many, many others, it occurs to me that perhaps we haven't been including a far more important section: Trust.

No other factor, it seems, plays as big a role in determining whether a project is completed on time and under budget, or whether it drags on interminably.

How do you build trust? What steps do you take to establish and maintain trust? How do you document in a proposal that if you don't have trust between the two organizations, you will be adding weeks or months to a project timeline?

It's all about trust. Plain and simple. Without it, you'll be hiking uphill with a backpack full of bricks. With it, you discover you've actually been wearing a jetpack full of rocket fuel. Up, up, and away! 

comments   permalink 




Computer News: Developers, Give .NET a Chance: "Many Java developers I know are quick to discount .NET as just the latest marketing hyperbole coming out of Redmond, Washington, the home of Microsoft. This attitude is unfortunate, because .NET may be the best thing Java could hope for in order to stabilize its own status as a development platform leader. "

We'll see. One thing I've learned is that business users usually don't give a crap about development tools. Java or .NET doesn't matter as long as they're able to get their jobs done with minimal headache from their computer systems. 

comments   permalink 




Thoughts on using Radio as a KM solution, especially as it applies to a consulting company, with employees spread out across the city:

  1. Install Radio on everybody's laptop or PC.
  2. Modify preferences so content is stored on an internal company server (either send instructions, or create a script to do this on multiple remote machines).
  3. Modify ITEM template to include authorname with each post.
  4. Create categories that relate to vertical "knowledge silos" within the company. Go with either technology categories (Interface Design, Data Warehousing, Security, Infrastructure, etc.), or by business (Retail, CPG, Banking, etc.).
  5. Finally, set up a daily e-mail content "push," sending the previous day's updates to everbody in the company (this way, nobody has to go "get" content).
Everybody can be a contributor, but it's not required. Everbody can be a consumer, but also not required. Contribution and consumption are both pretty easy to do, and when you put the two together, you end up with collaboration

comments   permalink 




I've got to get Radio installed on my home PC. It's currently running on my laptop, which tends to stay in the car over the weekend. There were more than a few times over the past couple of days that I'd wanted to do some writing (blogging? publishing?) but didn't because it was too cold to walk outside.

Well, too something, anyway. I think they have a word for that sort of thing. 

comments   permalink 



Copyright 2002 © Robert K. Brown

January 2002
Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31    
Dec   Feb