Two kinds of feedback for developers

Following along as Dave and Kyle unfold the already powerful Fargo outliner toolkit, I find myself wondering what kinds of feedback would be useful to them. Here is my guess:

The speed with which a writer can click the big + sign, compose a draft, save, and see it posted online convinces me that speed and ease are key to their vision. So I am guessing that any clues users can give about where the software is lightning-fast and intuitive, even for newbies, and where it is not, might help the team continue with their vision.

The range of tools already in place here convince me that they also want this to be a powerful, flexible toolkit that will amuse and and empower and gratify more experienced users. Here I am guessing that users can be valuable to the design team by diving in and starting to make cool things, sharing how they've done it, describing where they seemed to run into limits of the toolkit, dreaming big, and documenting their work in public as they go. This might take place on at least three levels:

  • Making sites that are technically cool and interesting.

  • Digging and exploring the collaborative powers of the toolkit.

  • Testing the powers of outlining as a web-linked solo writing tool.

Knowing Fargo even for these few weeks, we see that the team is thinking big, and we can honor that with the occasional thank you note but even more so by taking the tools as seriously as possible. And because this is a web-smart operation, documenting as we go.


Last built: Sun, Feb 23, 2014 at 10:53 AM

By Ken Smith, Friday, July 19, 2013 at 8:01 PM.