Office365 Small Business

Installed and started to configure Office365 Small Business Premium yesterday.  A little buggy and limited on guidance.  Still have a lot to cleanup on configuring; Issues with ID or Email Address, etc.  Guess that means there’s a market for someone to write a “how-to” book on install, configuration and operation.  Of course this has been one of the major deficiencies in Microsoft’s Business Model.  They can tell you how to flip switches on the product, but not how and why for your business.  The entire ITSM concept for Microsoft is still primitive which is why I keep getting questions from friends & family on how-to manage their IT environment.  Additionally that last several engagements I supported behind the scenes, customers where asking for the Microsoft equivalent of an IBM Redbook.  Unfortunately my old group was not chartered to fulfill such a request despite the growing need.  This suggests that when I’m finished my first book project, I start on a IT Operations Methodology and Guidebook similar to the Strategy and Market Planning methodology IP I developed for other Global 100 corps.

Today’s agenda is more physical office clean-up, troubleshooting structured wiring system, and Structure in Threes book layout wireframe design and if time permits back to configuring Office365 Small Business (wireframe layout for external site)

Advertisements

Moving Day#2 and my test bed Data Center: Part2

Taking a break from moving Dana’s office.  Got her desk & printer stand in place, computer, phone and printers setup and working.  Wireless connection fine, will have to troubleshoot hardline later.  Filing Cabinets & corkboards next.  Move going much faster than I expected.  Guess I’m getting use to moving offices of late.  Relaxing my back to the sounds of John DenverCountry Roads ), then lunch.  Later tonight I’ll update her Desktop with new Office via Office365 Small Business subscription I bought for her yesterday.   Should be interesting to see how she uses all the new capability and adjust to new Office; she’s still on Office 2007.  Though I got here a new laptop with Windows 8 and Office 2013, se really hasn’t touch it.

 

Revisting CRM for Independent Consultants

Business Development for Independent Consultants

Spent last night re-reading C.J. Hayden’s book Get Clients Now!  Awesome book for professionals and consultants that dread business development and marketing.  Ms. Hayden has put together a simple to use system to guide those of us in the mystical arts of business development and customer acquisition.  While it doesn’t guarantee you hundreds of clients banging at your door or millions from your first sale, it does provide some oft-times forgotten common knowledge and wisdom.  To get business you need to get known, to get known your have to get out there.  Ms. Hayden’s system guides you through identifying artifacts and activities you can do in a hour or so each day as part of her 28-day Marketing Program.  I remember the first time I read the book thinking I can do that, and I did.  This blog was one of the ideas she suggests in her book.  I work for a large corporation at present, however, I can see the core concepts being adapted for use here also.  In point most of the big CRM systems wish they had a imbedded process like this or Solution Selling, Keith Eades.  That said, the only drawback was its paper based, so I took to building a template to the Get Clients Now! approach last night.  Almost finished with the tracking spreadsheet.  I’m fairly happy with how its working out.  May upsize it to work on Office365 Small Business later:

Get Clients Now

More Cloudly Issues

With Microsoft suffering another outage with Office 365 potential enterprises must again evaluate the risks involved with going off-premise to the cloud.  I will not debate the proposed benefits of going to the Cloud.   The magic transformation of CAPX to OPX has to have every CFO pulling out their spreadsheets and CIOs examining the possibilities of elasticity.

http://www.zdnet.com/blog/microsoft/microsoft-heres-what-caused-our-cloud-outage-this-week/10381

These do come at a cost.  Increased risk.  While the infrastructure behind the cloud maybe resilient –depending upon the architecture used to implement the solution– Internet Access is still a potential single point of failure.  There are multiple places in the communications channel where glitches could take down an entire enterprise.  

Imagine your gateway is down.  On-premise this is not a problem, end users still have access to services behind the firewall.  Another possibility your provider is down, again access to all your services is at risk and then in the case of this latest glitch, and unconfirmed network appliance on Microsoft’s premises took the service down for three hours.

This is not an article bashing Azure or Office 365.  As an Enterprise Architect I find Cloud and specifically Azure a useful approach.  Actually before Cloud was Cloud I was writing articles about Virtual Corporations http://intelarbgrp.org/Documents/Engineering%20a%20New%20Paradigm.pdf using the Internet to create a virtual service infrastructure between corporations -and had demo’d some of these concepts at Autofact and prior to that discussing the digital nervous system at IBM Guide/Share conferences in the 80’s.

But like any tool its only as good as the skilled hands that use it.  What I mean by that is when considering a move to the Cloud multiple factors should be considered beyond reducing cost.  These factors need to be weighted carefully at the enterprise level and brought to the attention of business executives.      

 About a decade ago corporations when through a scare called Y2K, may companies spent millions on prevention.  One of the large Fortune 500 corporations clients I had the meter spinning with all the contractors they brought in to fix the possible issues.  They were concern that they were wasting money by the truckload and asked me to assist.  I developed an approach, or rather adapted a systems engineering approach [FMECA] toward Enterprise Architecture to help prioritize which systems to address as well as the urgency for each.  I later incorporated it in a revision of the Enterprise Architecture Methodology I co-developed and use today.

Simply put, looking at the Enterprise as a biological entity with various systems that support its health gives you a different perspective on the factors involved with cloud, on-premise, hybrid, etc.  Once this perspective is used multiple factors become clear as to the tradeoffs that should be expectedly address.