My last blog post about blist positioning and our new tagline may have been premature without our new supporting website.  For those customers who are reading this post through an RSS reader, and haven’t visited www.blist.com in a while, I urge you to point your browser to us and see the changes we’ve made.  We’ve changed our site to better communicate how consumers can use blist in their everyday lives.

I know what you might be thinking:  “Why bother creating ‘brochure-ware’ pages like this?  There are literally hundreds of products that are completely self-explanatory.  And generally, people don’t like to be ‘marketed to’.“  And you’re right, but…

At blist we are bringing a database to the mass consumer market.  That’s actually trickier than it sounds.  We have the interesting business problem (and I don’t mean problem in a pejorative sense) of being a Swiss army knife product.  blist is appropriate for many different personal and professional uses,  and sometimes those uses aren’t obvious to everyone.  It’s our job to make it 100% clear.

We think the new site accomplishes the important balance of getting the database-familiar customers immediately into the application, while still supporting the large segment of customers who like to read about a product or service before they sign up - even when an offering is free.

So, what do you think?  What do you like about the new site?  What could use some improvement? At blist we listen to customer feedback very intently….  And then we act on it.

Early to mid last century switchboards were manually operated by telephone operators, most of whom were women. In the late 1960’s Lily Tomlin endearingly characterized the role as Ernestine the telephone operator on Laugh-In. Advances in technology democratized the act of dialing a phone number and now we all do it ourselves.

In the 1960’s and 1970’s many corporations had pools of typists. If you needed to send someone a letter, you submitted your longhand request to the typing pool. Mini-computer based systems from Wang and Xerox replaced the typewriters with centralized word processing capabilities, but you still submitted your letter longhand to the pool. While these word processing systems were big advances over typewriters, they were still too expensive and too complex for the mainstream users. Remember, most typists had to be retrained on how to compose SGML in order to send special formatting instructions to the printer. Then in the 80’s, personal computers were adopted, followed at first by markup-based word processing software from Wordstar, then by WYSIWYG software from WordPerfect. These advances democratized the act of writing letters and we now take it for granted that we can write letters ourselves with Microsoft Word.

Number crunching followed a similar course. Accountants used paper spreadsheets to crunch numbers. If you needed some analysis, you asked the accounting group to develop paper models for you. Then in the 70’s McCormack & Dodge created electronic spreadsheet software for IBM mainframes. In the early 80’s software pioneers Dan Bricklin and Bob Frankston created the PC-based electronic spreadsheet VisiCalc, which later was supplanted by Lotus 123, which later was toppled by Microsoft Excel. Electronic spreadsheet software democratized the act of making financial decisions based on analysis of numerical data.

Art departments used to create foils for presentations. Making presentations has been democratized and we now take for granted that we can use PowerPoint to make presentations ourselves.

Engineering and architecture departments used to draw schematics and floor plans for us. Now with programs like Visio, we take for granted that we can create our own floor plans and technical drawings.

You could even argue that TypePad and WordPress have democratized creating simple web pages.

Why hasn’t working with data been democratized? In an odd paradox, IBM, Oracle, Microsoft and a handful of other companies have made powerful relational databases both ubiquitously available to enterprises yet out of reach to mainstream audiences. While advancements in technology empowered people to solve their own problems in all of the aforementioned areas, current database technology has failed to democratize the act of organizing and analyzing data. Instead of extinguishing a legacy profession, databases are so hard they’ve actually spawned a new profession - database administrators.

Why isn’t organizing and analyzing data as easy as creating an electronic document, spreadsheet or presentation? Stay tuned. Soon it will be. That’s exactly what we’re aiming to do with blist.

Web Office - What’s next? What’s innovative? Richard McManus has his Web Office 2007 Year in Review up today. The real trend in Office 2.0 has been on polish and refinement, and not on what you can really call innovation in a deep, Clayton Christensen sort of way. Exactly one year ago, I was playing around with Dan Bricklin’s Wikicalc, now part of Ross Mayfield’s Socialtext empire, today, I’m using Editgrid, and I frequently marvel at just how much of Excel’s functionality that it can supplant. Editgrid has the smoothest and most refined sharing and invite features that I’ve seen in a web office application outside of the Google Apps remora-like integration with Gmail, but at root, it’s still a spreadsheet just like those we have been using for 25 or so years.

So, again, my question is: what’s innovative on the web office horizon that is truly web-native from the ground up? Probably the most web-native applications out there are the various project management/internal blog/corporate wiki/IM packages that attempt to fill a nebulous and wooly space called ‘collaboration’. While more web-native than, ‘Word, only online’ - these products are really exercises in packaging and marking-up a few, well-established consumer web apps that have been around for 10 or so years. As any patent examiner worth her salt will tell you, munging up a bunch of prior art, while often useful, does not a non-obvious invention make.

Where do I think the real step-function innovation will come from as the progress cycle rolls over from a period of refinement to a period of invention? If I knew for sure, we could all go home right now, but since I don’t I can only speculate. My bet is that we will see far-reaching and paradigm changing innovation and impact from initiatives like SFdC’s ‘Salesforce to Salesforce’ and, oh okay, blist!

I’ve argued for a long time that world’s most ubiquitous database is Microsoft Excel. After all, Excel supports a large number of columns, a practically limitless number of rows, auto-filtering and sorting. So what’s wrong with Excel as a database? Here are 10 shortfalls to get the conversation started:

1) It’s cumbersome to store elemental data that might have more than one value per row. For example, let’s say you are using Excel to keep track of applicants for a sales position. You want to keep track of each applicant’s phone number. Most people have two or three phones now. How do you organize that in Excel?

2) It’s way too hard to create a pick list and use that pick list to populate cells. Maybe you want a column called stage in your applicant tracking system - Resume Received;Phone Screen;Interview;Extend Offer; etc. This is possible in Excel, but it’s unbelievably hard. Excel’s help describes how to do this in 9 steps. 3 of the steps are so hard, they hyperlink to another help page.

3) It’s not very visual. Just plain, old boring numbers and text. When I define a range as a date range, why doesn’t Excel embed a calendar control so I can pick a date from the calendar? When I try to insert a photo, why does it feel like it overlays my entire spreadsheet instead of inserting the picture into a cell? Why can’t I simply say that I want all the cells in column to have a checkbox?

4) It’s entombed on my PC. Yes, I can email to you. But now we each have separate copies. What if you update yours and I update mine? How do we reconcile those changes?

5) It’s not multi-user. What if you and I want to work on the database together at the same time?

6) I can’t create meaningful queries. What if I’m a VC and I want to construct a query like "Show me all startups who’ve been into the office for a meeting, were founded less than 12 months ago, are in Seattle and are not yet VC backed." If you have 20 or 30 rows in your Excel database, you can just eyeball it. But what if your deal pipeline tracker has 400 or 500 rows? How do you do that query in Excel (the answer is you don’t. It’s amazing how many VCs I know who are building this pipeline management system in house).

7) I can’t easily save and load multiple views of the same data. What if I have a list of 5,000 sales leads and I want to save some predefined views:

7.1) Leads rated "A" and not contacted in the last 45 days

7.2) Leads in the northwest (southwest, northeast, southeast)

7.3) Leads with an opportunity size > $50,000 and a probability of close > "Good"

7.4) Leads where stage changed to "Lost" within the last 30 days

7.5) Leads where stage equals "New" and Date Created is less than 7 days and source is "website" How do you save these views without bifurcating the raw data?

I can’t easily let someone casually subscribe to updates. If I’m the sales manager, wouldn’t I want to subscribe (via email or RSS) to the view in 7.4 above? Wouldn’t I want to know that as it happens? How do you do that in Excel?

9) What if I want a data entry form on my website to insert rows into my database in Excel? How do I do that, especially when my Excel database is entombed on my PC and my PC is turned off?

10) How do I relate two Excel spreadsheets to each other? If I’m trying to create a project list and I want to keep track of which tasks are assigned to which people resources, shouldn’t I be able to embed part of my people sheet into my project sheet? Of course you should, but making that happen in Excel is incredibly hard.

What we’re building at blist addresses all 10 of these Excel pain points very nicely. It’s as familiar as Excel but designed to be a collaborative, visual database. It’s the world’s easiest database. Have you tested the limits of Excel as a database? We’d love to hear your frustrations and encourage you to sign up for our beta.

Excel is two-dimensional. Columns run horizontally. Rows span vertically. Initially we think of data as having two dimensions as well. In fact, two key terms in database lexicon are rows and columns, just like in Excel. Here’s an example of what an Excel database of some fictitious people might look like:

In reality, however, data usually has three dimensions. Rows describe items. Columns are singular attributes of those items. Lists are plural attributes of those items. Observe how adding a column for the names of each person’s children necessarily morphs the structure into a third dimension. Here’s what that Excel database might look like with a list in a cell:

The way I’ve drawn that table is OK. The problem is that I had to grab each row and adjust its height manually.  Another option is I could have selected all the rows and navigated to Format –> Row –> Height and set the height for all rows to some arbitrary height. The problem with that, of course, is that the appropriate height differs from row to row. Jacob has three kids, Paul has two and Kim has one.

Maybe a better approach is for the software to allow you to enter a list of items in each cell, but be smart about how it shows you that data. Tighten it up. Maybe decorate it with a little triangle to suggest there’s more here than you see, but when you hover your mouse over the cell, show you all the values. Maybe it would like something like this:

What do you think?

I’m sure most readers of the blist blog are already passionate TechCrunch readers, but in case you missed it, blist was profiled on TechCrunch today. A lot of you have asked when we’re going to release some screenshots of our application and we agreed to let the cat out of the bag and show a sneak peek of some of the user interface. I encourage you to go check out the post and the screenshots if you haven’t done so already.

Just a quick post to congratulate the team on a great sprint. It was our best to date. At blist, we use a development methodology called Scrum. It’s designed to be lightweight and agile. Within the framework of Scrum we run two-week sprints. That’s a short development cycle. On the starting Monday of each sprint we have a kickoff meeting where we review a prioritized product backlog of features and the engineering team assigns cost estimates for each feature. Then we draw a line where the total estimate equals the total available man power. Everything above the line is what we hope to accomplish in the sprint.

Early in the development of blist we’d be lucky to penetrate 50% into the backlog in any particular sprint. I think we finished this sprint with something like 93% of the work items being completed. Hoowah! Great work, team! Our burn down rate was linear through the entire sprint as well. The burn down rate shows on a daily basis how many hours of estimated work remain relative to how many man hours are left in the sprint. Here’s what a sample burndown chart looks like:

We’re still not revealing too much about what it means when we say we’re building the world’s easiest database, but a few features completed in this sprint include:

* Lenses
* Simple search
* Multi-sided columns
* Preferences

I’m excited for Monday’s sprint kickoff meeting to see what we’re going to bite off in the next two weeks.

John Cook’s write-up on blist in yesterday’s Seattle P-I continues to circulate. I thought I’d chime in one more time and respond to a few comments and questions I’ve been getting via email.

First, I think people may be overly influenced by the title of John’s post. I would argue that Excel is the world’s most ubiquitous database. In that sense, blist aims to provide a much better environment for creating simple, visually rich databases. John asked me during the interview if we plan to add support for all of the functions Excel does. No way. I’m an avid Excel user and love all of its built-in statistics, math and financial functions. blist will offer some simple “column math” functions for things like creating a derived column. For example, if you were building a stock portfolio with columns “Number of Shares” and “Current Price” it makes sense that you would want a column called “Current Value” which is computed as “Number of Shares” x “Current Price”. We’ll also support some aggregate functions - sum, count, average, median, etc. I think of these as things you would expect in a database (and which are included in most databases). If Access were easier to use a lot of people would use it instead of Excel. We definitely see those people as our core audience. Of course Access and Excel were designed in the 80’s, before the Internet enabled us to work in much more distributed and collaborative ways. blist recognizes that and updates the delivery and collaboration model as well.

Second, our name isn’t derived from a river in South America or a Himalayan mountain. We all know that the word blog is a contraction for web log. Well, to be accurate it’s actually a portmanteau just like spork is derived from spoon + fork. Where we’re trying to innovate is on ease of use. We’re building the world’s easiest database. We wanted a name that conveys ease of use. We all already know how to make a list, so if we can make a list we should be able to make a web list - a blist.

Finally, are we like a webified version of Tableau Software? No. My understanding is that Tableau is not a database, but has some awesome visualization tools that allow you to see patterns and trends in your data as it resides in Oracle, SQL Server or some other data warehouse. When we use the word “visual” to describe blist, we mostly mean to convey that we have built-in types that let you store more than text and numbers. For example, pictures, music, documents, flags and stars can be stored. The visual effect is that when you look at your data, where appropriate its rendered graphically. You might create a corporate directory and have a column called “Mugshot” which shows the picture of an employee.

Today AdventNet, developer of the Zoho suite of lightweight office applications, launched Zoho DB. They already had a lightweight forms building, database application called Zoho Creator. Zoho DB is more powerful, especially considering that it understands SQL queries. Dabble DB and QuickBase are two other notable and well regarded web-based databases.

Throw the blist hat into the ring too. When we launch early next year we’ll compete with QuickBase, Dabble DB and now Zoho DB as well.

What strikes me most about the current offerings in the space is that they seem to have been designed for folks who love databases and there’s absolutely nothing wrong with that. While these solutions offer what might be thought of as an online version of Access, it’s important to observe that Excel is the most ubiquitous desktop database because Access is too hard for most people.

At blist our core design premise is that people want data, not databases. People want to see a product that moves us away from SQL, not towards it. We think you want a database that just gets out of the way and lets you create and share your data, connecting with others who are also passionate about whatever information it is that you’re organizing.

blist. Create, Organize. Share. Connect

A few weeks ago I received a phone call from a guy in Miami. Here’s how the conversation started:

- My phone rings.

- me “Hello, this is Kevin”

- Miami guy “Kevin Merritt?”

- me “Yep, Kevin Merritt”

- Miami guy “The same Kevin Merritt who once knew a guy named Neal Kaskel?”

- me “Um, uh, yeah” (this is weird, I’m thinking)

- Miami guy “Eureka! I’ve been hunting you down for weeks”

- me “uh oh”

- Miami guy “Are you the guy who made some software called Prospector?”

- me “Well, I led a team that built it, but yes Prospector was my baby”

- Miami guy “Great. I want to buy it. Can you sell it it to me?”

That odd conversation went on like that for another 20 minutes. Miami Guy wouldn’t take no for an answer, even when I told him that Smith Barney now owns Prospector and it’s not for sale as far as I know, not to mention 10 years out of date. He had to have Prospector.

Prospector is an application we designed and built between 1997 and 1999, when I ran IT for a 400-person investment bank. Smith Barney bought the company in 2001, in part because they thought Prospector was pretty cool and could use it in other parts of the company.

On the surface, Prospector was a multi-dimensional customer relationship management (CRM) system. It reflected our role as an infomediary (information intermediary) doing mergers & acquisitions (M&A). We didn’t buy a company and then sell it to a bigger company. We introduced sellers to buyers and then facilitated a deal being consummated.

Miami Guy recently started his own M&A firm. News traveled 3,000 miles from California to Miami. He heard that Prospector is unequivocally what you need to run an M&A firm.

The amazing thing about Prospector was that to its users it was a CRM system, but to its developers it was a platform for modeling, organizing, manipulating and analyzing data. No one on the dev team knew anything about CRM or investment banking, yet the people who used it thought it was the best CRM system you could ever invent for doing M&A. We didn’t create a malleable platform because we were smart. Rather, we built a platform because we really didn’t know what the app needed to do. We did what seemed natural - we delegated functional specification to business people.

Bringing this post back into context and 2007, blist has its roots in Prospector. We’re developing an innovative platform for modeling, organizing, manipulating and analyzing data. Want to track applicants or sales leads? blist will be good for that. Want to share your favorite recipes with friends? blist will be good for that too. Want to create your own VC done deals database? Yep. blist will be able to do that too. As importantly, you won’t need a DBA or even anyone in IT to get the job done. blist is for you, whether you’re from Miami or not.