1 / 22

How I Lost 30 Pounds Using GroupWise

How I Lost 30 Pounds Using GroupWise. Making GroupWise Indispensible t o Your Users and Customers. Introduction. Introduction. Who am I? Sean Kirkby Concentrico, Inc. (est. 1999) a.k.a. Armor Data Systems Worked with GroupWise since 1991. Introduction. Who is Concentrico?

aram
Télécharger la présentation

How I Lost 30 Pounds Using GroupWise

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. How I Lost 30 Pounds Using GroupWise Making GroupWise Indispensible to Your Users and Customers

  2. Introduction

  3. Introduction • Who am I? • Sean Kirkby • Concentrico, Inc. (est. 1999) • a.k.a. Armor Data Systems • Worked with GroupWise since 1991

  4. Introduction • Who is Concentrico? • Established 1999 • “Relax. Your GroupWise is Better Now.” • Experts in: • GroupWise API Development • GroupWise Implementation Best Practices

  5. Introduction • Today’s Topic: Losing Weight With GroupWise • What are you expecting from this session? • Of Houses and Hammers…

  6. The trouble with groupwise is…

  7. The Trouble With GroupWise Is… • For decision makers and influencers, what is the bottom line? • People getting things done. • The right things. • Enough things. • The right way.

  8. The Trouble With GroupWise Is… • What hinders attaining that goal? • Technical issues • Bad Tools • Hammers nails crooked. But… • Smashes eggs just fine! • Expensive Tools • Human issues • Stress • Too much to do, too little time/resources • Bad Health • Unhappiness

  9. The Trouble With GroupWise Is… • What hinders attaining that goal? (cont.) • Human Issues (cont.) • Lack of skills or information • Inability to make good decisions about doing things • Inability to use the tools.

  10. The Trouble With GroupWise Is… • Is GroupWise a Good Hammer, or a Bad Hammer? • Depends on the context • Hammers vs. Houses • Any tool is the wrong tool, if used incorrectly • No tool “does it all” • Every worker in every field has to compensate one way or another for weaknesses in their tools. • Our role • Novell’s role • Third party community’s role

  11. The Trouble With GroupWise Is… • Where Are GroupWise’s Greatest Weaknesses? • The Client • Does GW8 do enough? • Why is Outlook copied so much? • On being invisible: “The book has a feature which I think is hard to notice, but it’s the book’s most important feature. And that is that it disappears. When you are reading, you don’t notice the paper and the ink and the glue and the stitching. All of that dissolves and what remains is the author’s world.” -- Jeff Bezos on the “Kindle”

  12. The Trouble With GroupWise Is… • Third Party Support (API’s) • Two types: • Out of the box • Custom • Something radical has to happen to make this better. • Novell has to think like salesmen about this “You catch many more flies with honey than with hammers.”

  13. solutions

  14. Solutions • A Defined Context Makes It Clear • A “productivity system” must exist against which the tool, its use, and its products can be measured. • How do we measure GW’s success? • Does it crash? • Does it integrate? • Is it secure? • Is it cheap and easy to maintain?

  15. Solutions • How Should We Measure GW’s Success? • How do our customers measure it’s success? • Is it “invisible”? • Are people more productive? • How Do We Measure Intangibles? • Map system components to GW’s feature set • Measure it’s “invisibility” • Stability • Integration • Security • Maintenance

  16. Solutions • ProductivitySystems • Must be a specific system with defined principles and elements • Map GW to the system’s workflow • Features that map directly • Features that must be added • Custom Development • 3rd party • Things that must be done by things OTHER than GW • Involve the customer!

  17. Solutions – GTD® • Getting Things Done® • David Allen’s book • Basic premise: • “Your mind is not good at storing things” • You need a “trusted” system. • Managing work horizontally and vertically • Handling “actionable” and “non-actionable” items • Deals with physical and digital workspaces

  18. Solutions – GTD® • Basic Workflow • Collect • Process • Organize • Review • Do

  19. Solutions – GTD® • Things to Track: • “Projects” List • Project Support Material • Calendar • “Next Actions” Lists • “Waiting For” Lists • Reference Material • “Someday/Maybe” List • Checklists

  20. Solutions – GW to GTD® Map • An Example: Mapping GTD® • This is how I do it. • It’s important to identify how your customers need it • There are a lot of non-digital elements to my implementation. It works for me.

  21. Solutions – GW to GTD® Map • The (current) Manual Process • These things are NOT very invisible. • There is a LOT of room for improvement. • It’s better than not doing it. • A much more automatic process is in development.

  22. Solutions – GW to GTD® Map • Some Demos

More Related