Category Archives: 1990s

Rebooting the Knowledge Navigator

The following is a guest post by David Gleason, Silicon Valley veteran and storyteller extraordinaire.

davidgleason
Disrupting the Enterprise Experience by Starting with the User

After 30 years in the high-tech industry, I’ve come to believe that one of the great disruptions has been the transformation of the computer user, from someone who needed assistance, to the one who is calling the shots. No longer the passenger, the user is now in the driver’s seat and is setting the course. Successful entrepreneurs are those who, like the old joke about leadership, see a parade and run to the front of it, yelling, “follow me!”

In today’s enterprise, the user has evolved from being the source of input to the recipient of any desired output, anywhere, anytime without “directions.” This is part of what makes enterprise software so sexy at this stage – you can do almost anything with it, and you don’t need hand holding to get your work done.

When I entered this world as a technical writer in the 1980s, a knowledgeable friend, Rich Miller, told me: “The best way to create software is to start with the user manual — write what the program is supposed to do first, and then make the software conform to that.” He emphasized that this almost never happens, but it should — and the result would be a wonderfully easy-to-use product.

Today, the manuals are mostly gone, and in their place we are seeing an incredible explosion of user-centered design in areas that have long been hostile to the non-technical user. Giants like IBM, Oracle and SAP are improving the user experience on their systems, hosting content and forums on their websites,  and releasing smart phone apps that are snappy and cool and easy to use.

Small companies are carving successful businesses out of niche markets that once were the hidden domain of IT departments, like the help desk (Zendesk), travel and expenses (Concur), file sharing (Box), social collaboration (Jive) and many others.

Three decades ago, the question an entrepreneur was likely to ask was: Which markets or functions are most underserved by enterprise software?

Today those wishing to disrupt the enterprise software world are asking: which users are underserved by this same software, by the user experience, in fact, by the overall methodology used by the big enterprise software providers?

My personal experience tells me that the user has been put in control with the rise of the Internet, the browser and most recently, the smartphone with its apps, ecosystem, and “always on and at hand” availability.

Making Sense of Command-line Applications

My first job in the early 1980s was as a technical writer at ASK Computer Systems, a disruptive company in Silicon Valley that provided software for manufacturers to track costs, parts and projections. Customers included startups Compac, Sun Microsystems and Kurzweil.  The product, called ManMan (for manufacturing management), ran on HP 3000 and VAX 750 mini-computers which you accessed through terminals. Mini-computers were the disruptive hardware of their day, requiring far less expense than mainframes.

Using the ManMan system involved command-line data entry and multiple choice options, and the documentation was critical to understanding the product, how to use it and also how to track the constant software upgrades. Our pubs group cranked out thick binders of documentation, and we shipped updates to customers with individual pages containing edits that could be inserted into the binders.

In those days, the IBM PC was still a very new thing, underpowered and also command-line based. There were very few apps – unless you wrote them yourself. A big part of the tech writer’s job was to understand the user as someone who was mystified by technology. This meant explaining things in clear and simple language that most anyone could understand. Good documentation and training courses were essential to making enterprise software work.

The Rise of the GUI

The next disruption came with the rise of the graphical user interface (GUI) as a new and exciting approach to making computers both more visually rich and much easier to use. The operative word became “intuitive,” meaning you didn’t need to read the manual … at least in theory.In fact, Apple’s first Macintosh User Guide actually showed the reader how to “click and drag” with red arrows and detailed written instructions, since most users had no idea what it meant.

clickanddrag

“Click and drag” in the first Macintosh User Guide

Microsoft was converting command-line DOS to visually richer Windows as the computing choice for millions of enterprise workers, growing its developer platform and providing programming tools that encouraged software engineers to create thousands of powerful and useful apps that were easier to use, better at displaying information, and more timely than anything that ran on mainframes or mini-computers and required dumb terminals for display.

In 1992 — 3 years after the fall of the Berlin Wall — I attended Esther Dyson’s East-West High Tech Forum in Prague, along with hundreds of excited young entrepreneurs and engineers turned business people from Eastern European countries like Poland and Hungary.  Their world had been disrupted, state enterprises were being privatized and markets were being created in front of our eyes.

At a lunchtime presentation, Bob Epstein, VP of Sybase, showed the audience a database screen full of numbers, then converted it to a map of an oil pipeline where he clicked on a location and pulled up the information on flow and volume. He said, “we have to stop making the work look like the data, and make the data look like the work.” Now this was revolutionary! And very disruptive — you could actually make data look like something in real life.

gleasoneastwest

David at the 1992 East West Conference

Soon, all the big database companies including Oracle, Sybase, IBM and others, were moving to a rich GUI for easier use but also to be able to display more data.

The World-Wide Web

By 1995, we had shed the terminals, command lines and binders. It was all about the PC, shrink-wrapped applications and paperback books as Windows 95 took center-stage. Tim Berners-Lee had created the HTTP protocol and the World Wide Web;  the Internet is poised to become the next engine of disruption.

What I find most interesting is the way so many pieces came together and coincided with key turning points in hardware, software, business and even the fall of empires and the rise of new nations and markets. A new generation of users was accustomed to computing technology from their earliest years, so software developers could  keep adding features and functionality. As the Web expanded, the skills learned on the PC were transferred to the browser and the desktop computer was the single device for most users most of the time.

Everything at Your Fingertips

Today, the shrink-wrapped boxes of application software are largely a thing of the past. PC sales are flat and smart phones and tablets are growing at many multiples faster rate. Users are demanding much more than easy-to-use apps; they want massive amounts of dynamic, meaningful data at their fingertips — data that is relevant to whatever they are doing, and where ever they are, right now.

The enterprise services that power these apps have become quite amazing in their scope and power, but once again, we are seeing the best and most successful services are those that provide the easiest, most intuitive experience to users.  A great new service like Box.com is much more than file sharing — it’s an easy-to-learn experience because it builds on what most users already understand — the Web model of file access integrated with Tasks, Message, Chat and Group Collaboration — and lets you do things that you otherwise couldn’t do, and you can do them on any device or platform.

This time around the focus isn’t so much on teaching the user, but more on catching up with what the user has been wanting now for a while. So while the User Experience is still central, it’s a much more experienced, mature and sophisticated user that is demanding these new accommodations.

What does the future hold?

Twenty five years ago, Apple created a model of what the user experience could be like when data was abundant and accessible. It was called the Knowledge Navigator and the user simply told the computer what he wanted, and the system figured out where to find what was needed.

If you look at the trajectory of the past 3 decades, it’s hard not to conclude that the power of the user will grow, perhaps exponentially. I can see a future where the user no longer has to navigate applications or websites. Rather, we could be entering an age where the user simply tells a system or network of systems what she wants to do and the smart system finds the right tool for the job. It’s the realization of the Knowledge Navigator vision, an extension of making the data look like the work – and in an age of rich, dynamic, smart data, what could be more logical and useful than a system that can take your command and execute your wishes?

What are your thoughts on where the user experience is going?

 About David
David is a writer and senior content manager specializing in developer marketing and technical content creation for platforms, APIs and mobile. He has a life-long interest in the dynamics of change. His greatest thrill was meeting Russian physicist Andrei Sakharov in Moscow in 1988 with Apple executives on the 20th anniversary of the publication of Sakharov’s unauthorized book, Progress,  Coexistence and Intellectual Freedom. Sakharov’s book was a starting point for the social, political and economic upheaval that led to the fall of the Soviet Union, certainly a major disruption in world history.

Bill Wesemann: Sexy Has Come Full Circle

Silicon Valley veteran Bill Wesemann knows sexy. With over 30 years experience, Bill has done it all, from selling computing services in the pre-PC era, through running worldwide sales working for Steve Jobs at NeXT and an IPO at Genesys, to angel investing and advising today. Below, Bill shares his insights on how delivering and selling enterprise software has come full circle, as well as a surprising story about the darker days at NeXT.

How did you get started in technology?
“In 1981, I was a pitcher in the San Diego Padres organization in need of surgery.  (By the way, the lifestyle of a minor league baseball player is similar to working for a startup.  You sleep when and where you can, and if you win that night’s poker game, you upgrade to the buses’ spacious overhead luggage bin.) Waiting in the doctor’s office for my surgical consult, l picked up a copy of Forbes with an article that changed the course of my life. It featured the Top 20 information services companies, among which were several big players selling computing capability directly to end users, including Tymshare.  I decided on the spot that was my next step and before too long I’d landed the job I wanted in sales.”

What has changed since the sexy pre-PC era?
“What I find really interesting is what was sexy at the start of my career in the early 80s has come full circle.  What made Tymshare and its competitors so revolutionary was that the buyer was the end-user and didn’t have to be hardcore programmers to use our service.

Just prior to corporate adoption of the PC, Tymshare offered “fourth-generation” software that allowed analysts to quickly develop applications and empower the end user.  In addition to owning the X.25 packet network called Tymnet, Tymshare also had early versions of email for which we charged $0.25 for every 1K characters.  Can you imagine that cost structure today? Needless to say, with an uncapped pay-as-you-use model, the bills got very big, very fast. As companies struggled to contain costs and set standards, a new regime run by the freshly-created Director of MIS, emerged.  With increased PC adoption, early versions of fixed-price packaged software, and solutions moved in-house, the model unraveled. In 1984, Tymshare was sold to aerospace manufacturer, McDonnell Douglas.

Fast-forward 30 years, and with the advent of SaaS, cloud technologies, social, and mobile, and the end users are once again discovering their own solutions. With today’s multi-tenant SaaS architecture, the ability to deliver cloud services anywhere to any device, and cost-effective per seat or pay as you go pricing has taken the enterprise software industry by storm. As vendors like Salesforce.com have shown, it is more cost-effective, scalable, and flexible to use on-demand could-based software.  So we have come full circle, only this time the economics favor cloud-based applications.”

What’s sexy today?
“I think the rise of angel investors in the past decade has been very good for enterprise all around. Early stage investors can not only participate in advance of seed rounds, but can contribute more than money. Not only can I share domain expertise, but I am also a partner and true fan of the business and the founders.  While the interests of traditional VC models and what is best for the business can sometimes be at odds, angels can be more patient and understanding of the ups and downs inherent to an early-stage company. Because we can become personally involved with the business, I believe this trend will continue to have a huge impact on the success of a startup.”

You know this post wouldn’t be complete without a Steve Jobs story, right?
“Well, I figured.  Let me quickly back up to the time just before I went to work for NeXT and set the stage for a classic Steve story.

When Windows 3.0 put a GUI on enterprise applications, people could actually use them – talk about sexy for the enterprise!  Before applications were natively built with a GUI (think PeopleSoft in the late 80s), we sold tools to augment mainframe applications with a Windows or OS/2 GUI. I sold one of those companies, Viewpoint Systems, to KnowledgeWare, a computer-aided software engineering (CASE) company whose CEO was none other than hall of fame quarterback Fran Tarkenton.  When I joined NeXT, I went from working with a CEO who knew everything about sports and nothing about software to a CEO who knew everything about software and could care less about sports. Talk about 180-degree change!

I mention CASE because it sets the stage for a classic Steve Jobs sales call story.  You see, NeXT sold enterprise application development software, so he actually had to go on sales calls.  This particular meeting was a big one with the US Postmaster General. There we are in a room in Washington DC, 20 guys in suits and the two of us (Steve clad in his classic uniform, of course).  Their very first question was, “Steve, can you tell me what you think of CASE?”  I cringed, and a full 30 seconds of silence passed.  Steve then pretends he’s going to sneeze and says into his hand as loud as he can, “It’s bull shit”. I cannot describe the stunned looked on their faces. Another 30 seconds of awkward silence passes and I say, “Next question?”  I’ve got so many of these great stories, but we’ll save them for a future post.”

What did you learn working for Steve Jobs that applies to entrepreneurs today?
“I will say the time I worked with Steve at NeXT were tough times for him. Some had started to write him off and he was struggling to find himself.   Even through the darkest days, the only time I ever saw him really down was when he briefly decided to give up the user experience and adopt the Windows GUI over the beautiful object-oriented interface we’d developed at NeXT.  Obviously he ultimately didn’t have to do it, but he almost conceded.  It was his spirit and relentless drive that never allowed him to give up.

I believe that those that were fortunate enough to work for Steve at any point in time are the better for it. I have had the privilege of working for many great companies, but I look back at those days as the best of my career.  We worked every day with a singular goal of doing something unique and contributing to something special.  It may sound trite, but that type of culture and unwavering dedication makes financial rewards secondary.   We got up everyday to hit a grand slam.  We weren’t satisfied with a base hit and we never gave up.   I think this is an important lesson for any entrepreneur that faces the fire, you’ve got to double down on faith and push forward.”

About Bill 

Bill Wesemann is a Silicon Valley veteran with over three decades of experience in enterprise software. He began his career in technology in the early 80s selling computing services in the pre-PC era with several successful exits. In the 90s, he ran worldwide sales for NeXT, led sales at Genesys, which went public 1997, and was then CEO of NextPage.  For the past decade, he been an angel investor, advisor, and on the Board of Directors LivePerson (LPSN).  

 

seXML and Business Integration (what your parents didn’t tell you)

The following is a guest post by Jason Ouellette, CTO and Cofounder of SocialPandas.

My first startup job was as a junior engineer at webMethods in 1997. If you’re the kind of person who judges the passage of time by JDK version (and c’mon, who isn’t?) that’s the JDK 1.1 era. Although the details varied over the years, the mission of the company can be found in its camel cased name: to bring programmatic access to the web. The two technologies it used to do so: XML and HTTP. I’m going to jump into XML here because nothing says enterprise and sexy like XML.

XML had been proposed by the W3C as a kinder, friendlier replacement for SGML. Their XML 1.0 standard was structured, self-describing, “strongly-typed” and cognitively more accessible. The two founders of webMethods were excited about XML and its potential value in business integration, fanboi-level excited. They participated in standards bodies, conferences, and encouraged employees to contribute to new, related standards like XQL (XML Query Language, precursor to XPath). They even placed XML at the spiritual heart of our first product in the form of WIDL: Web Interface Definition Language, an XML dialect that described an API layer for CGI forms on websites. Or, in the interests of Keeping It Real: a language for writing web scrapers. However unglamorous it sounds, it made an impressive demo to ask the webMethods tool to examine a web page, build an API around it (like CORBA IDL, we would say enthusiastically), test it, and end up with a tidy, reusable XML description of the whole mess, importing the functionality of that website to any program.

A few months into WIDL we found that “Web Automation” (yet another euphemism for web scraping) was sadly not the Big Idea upon which we would grow big and rich like Netscape. No, we needed something less brittle and with more meat than the DHL and FedEx package tracking demos. We found it in B2B, namely Business-to-Business e-commerce. Using XML over HTTP we set out to improve the state of the art at the time, which was EDI (Electronic Data Interchange) documents over the VAN (Value Added Network). In comparison with the open and democratic interwebs, the VAN is a shadowy underworld of leased lines, arcane protocols like X25, and handshakes involving data formats that only a COBOL program could love.

A quick sidebar on EDI: In those ancient times of relative CPU and network I/O scarcity, many data formats and protocols were lean and mean, quite unfriendly to humans. They were optimized to live in the virtual space between computers, and space was tight. Some examples from the distributed computing wing of the IT museum: CORBA IIOP, COM/DCOM, and much higher up the stack, the ANSI X.12 and UN/EDIFACT family of EDI formats. If you’ve ever seen an “850” document you know it looks like petrified dino dung, but fixed-field documents like that are still hugely important today, helping businesses to exchange structured business information system-to-system, such as purchase orders and invoices.

In contrast to EDI, the human readability of XML business documents was one of its selling points, or so I observed on webMethods sales calls. It was not uncommon for raw XML to be shown in slide decks and demos to business people. While the IT folks in the room grumbled about its piggish appetite for memory and other computing resources, the less technical were transfixed with the beauty of its angle brackets. Fake but pretty purchase orders like this were often trotted out:

In addition to being transparent in a way that binary and fixed-field formats are not, XML documents can be validated against a Document Type Definition (DTD), the lightweight precursor to the more full-figured XML Schema specification. So before processing your purchase order for “Tasty XML Vittles” you can verify programmatically that it’s well-formed and will not break your e-commerce back-end (written in NetDynamics or some other cool web application technology of the day).

This was all sexy stuff back then. Many industries adopted XML dialects for e-commerce, like cXML for procurement and RosettaNet for high-tech manufacturers. webMethods sold lots of product built on the premise of XML document exchange over the Internet, went public (with its lovely WEBM ticker symbol), suffered Bubble Burst 1.0 (like $4B market cap one day, threats of Nasdaq delisting the next), and sold to Software AG for over $500M. XML went on to have a prodigious number of children, most with voluminous specifications, names like WS*. SOAP and Web Services live on today as the most mainstream incarnation of XML.

But like wholesome mid-century American family values, we still pine for the idealized simplicity of early XML. JSON (JavaScript Object Notation), a militant branch of the document simplification movement, has been sexy for a while now. I wonder what will come next, when JSON begins a course of Botox injections. That’s one of the fun parts of being in this industry. Knowing your history is optional, and you’re doomed to repeat it with faster machines.


About Jason

Jason has always preferred computers to people; so starting at age 6 he was coding Commodore BASIC and 6502 assembly. As Chief Architect at Appirio, he wrote three of the most popular apps on Salesforce.com’s AppExchange as well as a book for developers about Force.com. At data virtualization vendor Composite Software, Jason led R&D efforts to build connector products for SAP, Siebel, and salesforce.com. As a founding engineer at webMethods (now Software AG), he developed the industry’s first XML-based B2B integration server. He has a B.S. in Information & Decision Systems from Carnegie Mellon, and graduated summa cum laude from the San Francisco School of Home Renovation Hard Knocks in 2009 with his thesis, “The Information Asymmetry of Milestone Payments.”

 

It’s time for me to confess…

I think enterprise software is sexy as hell.  There, I said it. I think creating value that customers will pay for is extremely hot. A recurring revenue stream makes me giddy.  And nothing, absolutely nothing, turns my head more than profitability.

Why is enterprise boring by definition?  How can improving or changing the way people do business not get you fired up?   Even when I was a noob to the Valley, I still preferred business over consumer. Maybe it’s just because I don’t understand consumers or I don’t want to fall prey to their fickle nature.  Maybe I really am just old and boring and can’t accept it.  Or maybe it’s because I grew up in the age of SaaS.  At my first startup in 1998, we didn’t even know what to call it. We said, “Um, it lives in your browser.” [Blank stare.]  “You can log in from any computer, even from home.” [Furrowed brow.]  Our incumbent competitor wasn’t just premise-based, but kiosk-based, so it was a mind-bending concept for our prospects to grasp. At some point these magical services became ASP, then on-demand, then SaaS, and now we’re all happily living in the cloud – until the next rebrand.

The inspiration for this blog came after reading a great article in TechCrunch where Alexander Haislip explains that the model to follow is not Instagram, but companies that have “real intellectual property, obvious monetization and a plethora of cash-rich potential acquirers.”  I loved Alex’s contrast on the statistical exit probability and valuations of consumer and enterprise markets…. but it was the reader comments that hooked me. It was a lively debate and I’d wager I could guess the age of each commenter within 5 years.  And then I found the one that struck a nerve, “God in Heaven, I don’t know ONE techie who WANTS to build that crap!”

Crap? Really?

As I sat ranting in my head about how these SoLoMo app building, Red Bull drinking, freemium loving, hoodie wearing twentysomethings don’t have a freakin’ clue, it hit me – I am a complete hypocrite.  I cannot count the number of times I’ve turned up one side of my lip while emitting an audible sound of disgust at the thought of working for a global, lumbering, legacy enterprise like Oracle or Cisco. How could that enterprise be my enterprise?   I realized that, just as the newest generation of entrepreneurs and enthusiasts have little understanding of what’s come before them, I’ve completely failed to pay homage to all that came before me. … and what those companies did to empower our generation to build the next great thing on top of their achievements.

When I joined the “dotcom” ranks, we were revolutionizing the world with “the Internet,” turning tradition on its ear, changing the way the world communicated, and had zero respect for anything that got in our way.  In hindsight, it’s clearer to me that while all of that is true, we owed that opportunity to the trailblazers that made our revolution possible.  Without the on-premise and client-side software providers, what improvements would we have had to offer with our fancy new SaaS-iness? Without the hardware, database and communications infrastructure, what would we have built upon? The big boring behemoths are behemoths precisely because our world can’t run without them.  Remove that infrastructure and our apps, enterprise or otherwise, grind to a screeching halt.

I’d also venture to say that this generation’s arrogance is completely justified.  Social and mobile are absolutely revolutionizing how the world connects and interacts.  It did, however, take a lot of once-alluring hardware innovation and uber-sexy enterprise (and consumer) software to get here.

Thankfully Aaron Levie has declared enterprise is sexy “again” (twice!). And even if Dustin Moskovitz and Drew Houston haven’t explicitly declared their infatuation they (along with others) have certainly done it in deed. Yes, fanboys, someone can voluntarily leave Facebook for enterprise without dying of boredom. And just for the record, I love SoLoMo apps, Red Bull and hoodies.  Just don’t get me started on freemium unless you’re ready for an earful. It’s a topic for an upcoming blog.

Here’s my point: From mainframes to mobile, everything that has value was sexy at some point, even if that’s no longer the case.  This blog will feature interviews and guest posts from everyone along the way.  Tales from the trenches, lessons learned, and a timeless perspective on who and what has contributed to creating the industry I love.

Wanna share your sexy story through a guest post or interview?  Let me know in the comments or connect with me on Twitter.

Special thanks to David “The Punctuation” Gleason for his Wikipedia mind, colorful insight and masterful editing prowess.