Boxes and Arrows: Comments by Jordan Frank

Jordan Frank — Fri, 26 Jan 2007 14:53:12 GMT

Effectively, Web 2.0 is an organic, ever changing fabric knit based on collaborative efforts of the many. AJAX implementations make interacting with web interfaces speedier, in one sense, but more importantly can allow for widget type mini-applications to live within hypertext pages.

Deployment of Web 2.0 in the enterprise begs the next question: What is Infrastructure 2.0? Enterprises are likely to make a move from consolidating to single data repositories to supporting distributed architecture, distributed storage, distributed applications, and decentralized taxonomy.

Far from a mess, this architecture works well on the web and can work on the enterprise with consolidated directory, good server infrastructur and a keen understanding of how Web 2.0 deploys given a permission based architecture vs. the “everyone can read” nature of the open web.

My notes from Burton Group’s catalyst conference elaborate on these points: http://traction.tractionsoftware.com/traction/permalink/B…

Jordan Frank — Sun, 11 Mar 2007 18:55:30 GMT

In reference to a Burton Group report on the subject, I blogged about the importance and utility of hypertext as the core for interactive and compound “documents” where, in essence, the idea of a document dissolves, replaced with a set of mechanisms for joining pages and data in the manner that is required given a certain context.

In the context of project requirements, you could have hundreds of separate pages that you need to allocate and re-allocate across milestones, then produce “document” views which slice the requirements by milestone or even by status.

read the full entry here

By the way: 1 month ago, my inbox dropped to 2 messages. A business trip caused me to let it slip into the 20s but I will get back down to 1 or 2 by end of week. My tools:

1) Traction for all the text content that I need to remember, share or track/manage
2) ACT to record contact actions and next actions.
3) A spreadsheet for a few simple needs like managing my trade show calendar and tracking sales

Jordan Frank — Thu, 15 Mar 2007 17:01:02 GMT

I was a product manager at Adero and then Inktomi. Requirements were generally written in a Word document which got bigger and bigger and increasingly more impossible to manage. Worse was communicating small changes which occurred frequently. Now I am at Traction where the process is a world apart. We do this interactively with 1000s of requirements pages that are individually marked with release milestones and can be reallocated with a button click. And documentation representing a snapshot in time (if required) can be produced instantly. This wiki style approach is a totally different model than folks are used to, but it is, without doubt, the future approach. For additional context, Read this bit on Wiki vs. Blog and this bit on compound documents.