My Day as Mark Lewis

Another quick little post.  Working on some other posts, but I wanted to get this out.  This is a list of things I would do if I were in charge of IIG and had the funds to do what I wanted.  Obviously I am not going to have that job or the funds, but this is fun.

  1. Rename the Intelligent Case Management product family to Intelligent Content Management.  After all, isn’t Case Management something you build on top of an intelligent content server with a nice configurable xCP framework?  There are other solutions that fit there as well.
  2. Give Victor Spivak a Keynote at Momentum. Victor is great and we love to hear him talk about how things work.  He could talk about the cool plans for the backbone of the future of Content Management.  At the end, bring in Jeroen van Rotterdam to do some demos.  It is extremely entertaining to watch him when he himself isn’t always sure that the demos will work. (tip of the cap to Chris Campbell for this idea)
  3. Build xCP 2.0 on the Next-Gen Content Server for D7. This is the funding concern.  Victor didn’t say when, but with all the qualifiers he gave, I expect that the move to xDB in the backend is not near-term.  It should be.  I’ll explain why in more detail in a later post, but there is a lot of money to be made by putting an Intelligent Content Server in the cloud.  My family photo album may be a commodity and free to store online, but my company records with retention policies and content analytics identifying trends will not be free for quite some time.  Imagine being the first DoD 5015.2 certified RM system that runs, and is certified, in the cloud.  Marketing legs that will last a long time.
  4. Take Momentum back to New Orleans.  Let Tucci bring EMC World if he wants.  No more Vegas or Orlando.  Let’s go somewhere fun and new.  Three words on the 2003 conference: Best. Conference. Ever!
  5. Separate non-Webtop UIs from the Content Server release schedule.  Let the client applications release more often and have shorter testing cycles.  Allow them to innovate.  You’ll never make them feel like the latest web apps, but you’ll keep them within a year or two.  With Webtop, and whatever follows, you have to keep at least one app that can deliver everything the Content Server provides.
  6. Bring the Users back to Momentum.  I used to attend Product Advisory Forums.  Not just to give feedback on the roadmap, but to give ideas for the roadmap.  The first day had tutorials for those that were getting started with a new product line, introducing it, the concepts, and how to use it.  Half the sessions were case studies, presented by business users.   There used to be 6 tracks with more sessions per track than there are now, and that was before the developer conference was merged.  Market to the business users.  Give them the speaking slots.  Reward sales reps if they get multiple customers to present.
  7. Attend Momentum Europe.  Never gotten to go, but I bet if I was in charge they would let me attend.
  8. Refuse to conform.  I already do this.  In fact, the only reason I have this item in here was to get the list to 9, which is neither 8 (AIIM) or 10 (Letterman).  The point is that the product that just conforms will never lead, never generate excitement, and will never have the world hanging on every word that the President of the company says.
  9. Create a Vision and Share it with the World.  I’d craft some awesome vision and share it.  I’d push to achieve it.  I’d do whatever I could to make my enthusiasm for the vision contagious.  I would create excitement in the industry about my products.  People may still circle the date for SharePoint 2013, but they would also be circling the date for D7.

Of course, then my day would end and people would go back to what they were doing before I arrived.  The would head to the bars talking about that nut that snuck in and sat at Mark’s desk all day.

6 thoughts on “My Day as Mark Lewis

  1. JW says:

    Excellent post. I elect you Mark-for-the-day (as if I have that power… but this is _fun_, right?).

    Like

    • Thanks for the vote. Your not a shareholder are you? 😉 One thing I forgot was going to Rotterdam to hang with the xDB team. That would be fun productive.

      Like

  2. Chris Campbell says:

    I’ll add a tenth: 10. Simplify the product version numbering between the applications and xCP. I know it just isn’t me that’s easily confused by it and I could see the frustration in many of the presenter’s faces whenever the product timeline slide would show up. See if this makes sense:

    Currently, applications are at version 6.5 SP3 and the xCP platform is at 1.0. When D6.6 is released, then xCP will be at 1.5. Then next year, D6.7 rolls out with xCP being labeled 1.6. When D7 rolls out, xCP will be at 2.0.

    or
    D xCP
    6.5 -> 1.0
    6.6 -> 1.5
    6.7 -> 1.6
    7.0 -> 2.0

    I’m going to get really confused. I just know it. Then throw in DSS 1.0 in the mix then there’s another version to keep track of. If it takes three minutes to explain the versioning sytem between the two, then that system isn’t working.

    Since xCP is an application composition platform, and not just one application, why not just make xCP version numbering conform to what’s already there? Or (don’t know how this will go over…) hit the reset button at D7 and rebrand/restructure the entire application stack. Composer looks like it’ll consolidate a few things by then so it’s the perfect opportunity.

    In my opinion, the current numbering is a mish-mash of two systems that makes me uncomfortable. Sorta like eating the perfect Chipotle burrito, but having a bit of heartburn afterwards.

    Like

    • How about I hire Chris Campbell to fix the version numbering mess. That looks suspiciously like real work. 🙂

      Like

  3. Aha – two of your items are inextricably linked:

    “Best. Conference. Ever” – not if you had been to Momentum Europe ! Barcelona or Rome, take your pick…… B E S T C O N F E R E N C E E V E R !!

    I have physical and psychological scars to prove it….. (Italian taxi drivers!)

    Like

Comments are closed.