If you're going to collaborate, you will likely want to share electronic documents. And you probably already use one if not several tools for creating, editing and storing those documents. So the last thing, and I mean the VERY last thing you and your colleagues want and that your business needs is yet another application to facilitate document sharing and collaboration.
What you really want is a solution that enables these abilities in ways that are, as the most popular and valuable business IT features always become, pervasive, ubiquitous and invisible. From a more technical perspective, what you want and need looks and feels a lot like middleware -- software that users never see or touch, but that makes the tools and services they do touch work better together.
From this perspective, I believe that I have seen the future, or at least one strongly compelling future, where document-centric collaboration is concerned. I believe a harbinger of that future is CloudPointe, which has just introduced a cloud-based service that enables users of Amazon.com S3, FTP, Google Docs, Microsoft SharePoint or Secure FTP (SFTP) to share, collaborate with and store documents easily and securely.
For more details, I direct you to a recent SYS-CON article on CloudPointe by my industry colleague and fellow Focus Expert Network member Tim Negris. You can find the article at http://dortchon.it/CloudPointe, and you should read and remember it, even if you never become a CloudPointe user. Tim makes several points about what's needed for effective document sharing and collaboration -- points I've decided that I don't need to make here if you read his article, because I enthusiastically agree with all of them.
Check out Tim's article, and let him (and me!) know what you think. Ditto regarding CloudPointe. Sometimes, it's true that the future is now, and I believe now is one of those times.
Showing posts with label Google. Show all posts
Showing posts with label Google. Show all posts
Tuesday, November 16, 2010
Tuesday, August 24, 2010
Business Applications, Faster, Cheaper & Guaranteed -- EnterpriseWizard CEO Colin Earl: The Dortch on Collaboration 3-Q Interview
In many companies, the most business-critical collaborations today take place via highly or totally custom-built applications. This is especially true at lager enterprises, and thanks in part to cloud computing, it's increasingly true for smaller companies as well.
Two increasingly critical challenges to effective, money-making, customer-delighting collaboration immediately leap to mind:
I thought Colin might have some useful thoughts on the current state and near-term future of business application-building. And I was right, as you'll read below. (I've added links to appropriate Wikipedia definitions and other resources rather than inserting a bunch of distracting explanations for some of the terms Colin uses. You're welcome.)
Q1: What is the greatest challenge facing business application builders today?
A1: Time/Cost. The business manager might say "We just need to manage XXX". He/she thinks of it in terms of a simple Web interface and expects that it should take a few days or weeks to complete.
But to meet corporate standards and government compliance, it also needs a ton of back-end and reporting functionality, such as: auditability, dashboards, automated backups, security, [support for] Web services/REST APIs, graphical charts, searching, synchronization with other systems, data integrity constraints, database connectivity [and] export/import capabilities. The list goes on and on.
By the time they have finished and debugged all this, the "little" project has taken man-years, cost a million dollars and may well be obsolete because requirements have changed.
Q2: What is the greatest challenge facing providers of tools and solutions for business application builders today?
A2: Providing a compelling value proposition. The old proposition of "Invest in months of training so that you can build applications that only the original developer can maintain" is no longer acceptable, especially when it involves some proprietary language.
With the possible exception of Microsoft, no single company can really afford to keep their proprietary technology apace with the rate of open-source development stacks. The LAMP [Linux/Apache/MySQL/PHP] and open-source Java stacks are simply evolving too quickly. Compare the rate at which Android has developed, as compared to the Microsoft smart-phone OS (assuming you can still find a Microsoft-based phone).
Tools and solutions for business applications builders must therefore leverage the open-source stacks, while adding compelling value.
For example, the tool might automate provision of all the "standard" functionality such as auditability, dashboards, automated backups, etc. The developer could then focus on development of the user interface and specialized business logic, so that the whole application could be built in a matter of weeks.
Q3: What is the "next big thing" in the building of enterprise applications -- technological, cultural or other?
A3: Removing the need for hand-coding. It is not only a huge time-sink, but the source of most problems.
The Google App Inventor [for Android] is doing this in the smart-phone space and we are doing it in the enterprise application space.
Let’s examine the main reasons that CIOs are fired, as described in a 2009 CIO Strategy article:
Project never gets finished or goes too far over budget. (Removing the need for custom coding reduces the time required to develop a project by a factor of four or more.)
Major application failure. (If the tool allows the project to be developed using the functionality built into the core platform, then it will be leveraging a code set that has been tested for scalability, audited for security and proven in hundreds of enterprises worldwide.)
Non-compliance or a high-risk issue compromises the organization. (Compliance support can be automated with a tool that only shows an auditor what a defined business process is and how the system enforces it, but how the process has been followed in any particular instance. The framework can capture and collate data, such as who logged in, what IP address they came from, what records they viewed, edited, etc.)
There are further advantages [when the need for hand/custom coding is eliminated]:
One of the major drivers of IT into the heart of almost every business on the planet was this intentionally vague value proposition: automate/eliminate mundane tasks and let people concentrate their skills and efforts on higher-value activities. As technologies for building, tailoring and deploying applications have evolved, "programming" such applications is increasingly becoming more mundane than unique and creative.
Of course, that means the "programming" of tools such as App Inventor for Android and EnterpriseWizard must result in tools that are powerful, yet relatively simple to use for those building and tailoring applications. Colin and his team, like the team at Google Labs building and refining App Inventor for Android, understand the criticality of combining power, flexibility and simplicity in a balance that favors, supports and empowers users.
Companies seeking to build premise-based or hosted/cloud-based applications that improve competitiveness and agility without requiring extensive programming or IT support resources should look closely at solutions such as App Inventor for Android for mobile applications and EnterpriseWizard for others. The better your business applications, and the fewer resources you have to spend on building, running and improving them, the better the collaborations your company translates into revenue and profit. You have little to risk, and much to gain, by exploring such solutions now.
Two increasingly critical challenges to effective, money-making, customer-delighting collaboration immediately leap to mind:
- getting apps built, deployed and tailored as needed rapidly and cost-effectively; and
- getting and keeping those those apps aligned with critical, subject-to-sudden-change key business processes.
I thought Colin might have some useful thoughts on the current state and near-term future of business application-building. And I was right, as you'll read below. (I've added links to appropriate Wikipedia definitions and other resources rather than inserting a bunch of distracting explanations for some of the terms Colin uses. You're welcome.)
Q1: What is the greatest challenge facing business application builders today?
A1: Time/Cost. The business manager might say "We just need to manage XXX". He/she thinks of it in terms of a simple Web interface and expects that it should take a few days or weeks to complete.
But to meet corporate standards and government compliance, it also needs a ton of back-end and reporting functionality, such as: auditability, dashboards, automated backups, security, [support for] Web services/REST APIs, graphical charts, searching, synchronization with other systems, data integrity constraints, database connectivity [and] export/import capabilities. The list goes on and on.
By the time they have finished and debugged all this, the "little" project has taken man-years, cost a million dollars and may well be obsolete because requirements have changed.
Q2: What is the greatest challenge facing providers of tools and solutions for business application builders today?
A2: Providing a compelling value proposition. The old proposition of "Invest in months of training so that you can build applications that only the original developer can maintain" is no longer acceptable, especially when it involves some proprietary language.
With the possible exception of Microsoft, no single company can really afford to keep their proprietary technology apace with the rate of open-source development stacks. The LAMP [Linux/Apache/MySQL/PHP] and open-source Java stacks are simply evolving too quickly. Compare the rate at which Android has developed, as compared to the Microsoft smart-phone OS (assuming you can still find a Microsoft-based phone).
Tools and solutions for business applications builders must therefore leverage the open-source stacks, while adding compelling value.
For example, the tool might automate provision of all the "standard" functionality such as auditability, dashboards, automated backups, etc. The developer could then focus on development of the user interface and specialized business logic, so that the whole application could be built in a matter of weeks.
Q3: What is the "next big thing" in the building of enterprise applications -- technological, cultural or other?
A3: Removing the need for hand-coding. It is not only a huge time-sink, but the source of most problems.
The Google App Inventor [for Android] is doing this in the smart-phone space and we are doing it in the enterprise application space.
Let’s examine the main reasons that CIOs are fired, as described in a 2009 CIO Strategy article:
Project never gets finished or goes too far over budget. (Removing the need for custom coding reduces the time required to develop a project by a factor of four or more.)
Major application failure. (If the tool allows the project to be developed using the functionality built into the core platform, then it will be leveraging a code set that has been tested for scalability, audited for security and proven in hundreds of enterprises worldwide.)
Non-compliance or a high-risk issue compromises the organization. (Compliance support can be automated with a tool that only shows an auditor what a defined business process is and how the system enforces it, but how the process has been followed in any particular instance. The framework can capture and collate data, such as who logged in, what IP address they came from, what records they viewed, edited, etc.)
There are further advantages [when the need for hand/custom coding is eliminated]:
- User adoption is a lot easier with a system that can be rapidly adjusted based on their feedback.
- If there is no custom code, there are no code-compatibility issues with upgrades.
- Business managers no longer need to agree with one another on everything six months in advance. After all, the system can be changed using just a browser in a few hours. They are also no longer dependent on the “common sense” of programmers to deliver the system they need.
- The system is self-documenting because everything is exposed through the admin browser.
- Data integrity is automatically maintained by the system, not by custom code.
- Code maintenance accounts for 80% of the cost of software projects. With no code to write, there is no code to maintain so cost, hassles and unpredictable delays are eliminated.
One of the major drivers of IT into the heart of almost every business on the planet was this intentionally vague value proposition: automate/eliminate mundane tasks and let people concentrate their skills and efforts on higher-value activities. As technologies for building, tailoring and deploying applications have evolved, "programming" such applications is increasingly becoming more mundane than unique and creative.
Of course, that means the "programming" of tools such as App Inventor for Android and EnterpriseWizard must result in tools that are powerful, yet relatively simple to use for those building and tailoring applications. Colin and his team, like the team at Google Labs building and refining App Inventor for Android, understand the criticality of combining power, flexibility and simplicity in a balance that favors, supports and empowers users.
Companies seeking to build premise-based or hosted/cloud-based applications that improve competitiveness and agility without requiring extensive programming or IT support resources should look closely at solutions such as App Inventor for Android for mobile applications and EnterpriseWizard for others. The better your business applications, and the fewer resources you have to spend on building, running and improving them, the better the collaborations your company translates into revenue and profit. You have little to risk, and much to gain, by exploring such solutions now.
Tuesday, July 13, 2010
Collaboration, Communication and Business Processes: Why They're Connected and How to Get Them There, in 13 Sentences!
1. Every business relies on collaboration and communication to do business.
2. Almost all business collaboration and communication is supported by some form(s) of information technology (IT), whether e-mail, social media telephone or even fax.
3. To win consistently and thrive competitively, businesses need to be able to do the right things for customers, partners and prospects consistently and respond to changing requirements or conditions in a timely, agile fashion.
4. Ad hoc, inconsistent collaboration or communication practices make it unlikely to impossible for businesses to do what they need to do to win consistently or thrive competitively.
5. The key difference between collaboration and communication practices that help a business to win and those practices that don't are consistent business-driven processes implemented and enforced across all business-critical activities and actors.
6. Processes that are crafted, documented and enforced well and consistently help to ensure that all important actions contribute to satisfaction of customers, partners and prospects and business success.
7. At most businesses, critical processes are often inconsistently and poorly crafted, documented and/or enforced, when they exist, are documented or are enforced at all.
8. The businesses best able to capture, define, implement, enforce, integrate and manage critical processes are those best positioned to win and to thrive competitively.
9. A potentially powerful way to achieve these goals is to process-enable the collaboration and communication solutions upon which the business already relies and with which users are already familiar.
10. Fortunately, new IT tools are appearing that make it relatively easy for even non-technical business decision makers to capture, define, implement, enforce, integrate and manage business processes effectively and consistently, and to process-enable key collaboration and communication solutions.
11. Examples include Cordys, which offers cloud-based process and workflow management that integrates with Google's online office applications, and EnterpriseWizard, which combines cloud- or premise-based application building and process capture/creation with an unconditional money-back satisfaction guarantee.
12. Your business needs to begin by capturing, analyzing and optimizing all critical incumbent processes, evaluating and prioritizing key collaboration and communication solutions and mapping out how best to process-enable these -- preferably now if it hasn't already.
13. For more on this (and on EnterpriseWizard), read my recent Focus Brief at http://focus.com/c/B3E/; to discuss, feel free to drop me a line at mdortch@focus.com and/or at medortch@dortchonit.com.
2. Almost all business collaboration and communication is supported by some form(s) of information technology (IT), whether e-mail, social media telephone or even fax.
3. To win consistently and thrive competitively, businesses need to be able to do the right things for customers, partners and prospects consistently and respond to changing requirements or conditions in a timely, agile fashion.
4. Ad hoc, inconsistent collaboration or communication practices make it unlikely to impossible for businesses to do what they need to do to win consistently or thrive competitively.
5. The key difference between collaboration and communication practices that help a business to win and those practices that don't are consistent business-driven processes implemented and enforced across all business-critical activities and actors.
6. Processes that are crafted, documented and enforced well and consistently help to ensure that all important actions contribute to satisfaction of customers, partners and prospects and business success.
7. At most businesses, critical processes are often inconsistently and poorly crafted, documented and/or enforced, when they exist, are documented or are enforced at all.
8. The businesses best able to capture, define, implement, enforce, integrate and manage critical processes are those best positioned to win and to thrive competitively.
9. A potentially powerful way to achieve these goals is to process-enable the collaboration and communication solutions upon which the business already relies and with which users are already familiar.
10. Fortunately, new IT tools are appearing that make it relatively easy for even non-technical business decision makers to capture, define, implement, enforce, integrate and manage business processes effectively and consistently, and to process-enable key collaboration and communication solutions.
11. Examples include Cordys, which offers cloud-based process and workflow management that integrates with Google's online office applications, and EnterpriseWizard, which combines cloud- or premise-based application building and process capture/creation with an unconditional money-back satisfaction guarantee.
12. Your business needs to begin by capturing, analyzing and optimizing all critical incumbent processes, evaluating and prioritizing key collaboration and communication solutions and mapping out how best to process-enable these -- preferably now if it hasn't already.
13. For more on this (and on EnterpriseWizard), read my recent Focus Brief at http://focus.com/c/B3E/; to discuss, feel free to drop me a line at mdortch@focus.com and/or at medortch@dortchonit.com.
Wednesday, October 28, 2009
Microsoft Office Web Applications Arrive: Is It Finally Time for Your “Office in the Cloud(s)?”
Microsoft has begun rolling out something many of us in the punditocracy have long viewed as inevitable but unlikely – Web-based, so-called “lightweight” versions of its flagship Office programs. The debut is so far limited to a subset of the Office suite, and to invitees only, but the implications for collaboration – and for the venerable, nearly ubiquitous Microsoft Office itself – are already significant.
Microsoft is in fact focusing largely on support for collaboration with its Office Web Applications. They’re accessible via Internet Explorer, Firefox or Apple’s Safari Web browser (but not Google’s Chrome, at least so far), and the Web-based version of Excel already supports multi-authoring, or simultaneous editing of the same workbook by multiple collaborators. Users can’t yet create Word documents, but should soon be able to create and collaborate on all types of Office documents.
Microsoft plans to make Office Web Applications available in three different modes. Subscribers to its Windows Live service will have no-cost access. Users of Microsoft Online Services will be able to purchase subscriptions. And companies licensing Microsoft Office 10 will also be able to license and provide access to Office Web Applications.
I expect these Microsoft offerings to be very popular, especially at companies seeking to reduce or halt the growth of their licensing and support contract costs for Microsoft Office. Many such companies have deployed or begun exploring other online alternatives from Adobe, Google, Zoho and elsewhere. However, these all offer mixed bags of interoperability and compatibility with native Office applications and file formats. So an online suite from Microsoft should eventually offer an alternative that does not suffer from such limitations. But those other online office/productivity suite providers aren’t going to stand still either.
Microsoft’s official entry into the online collaboration suite market will definitely make the market more interesting. Whether it will benefit Microsoft as much as or more than its cloud-based competitors remains to be seen. But where users are concerned, more online collaboration choice is definitely better, especially if it comes with more seamless interoperability with all of those Microsoft Office files most of us rely upon every day to do business.
If you want to know more, check out these two Focus Research Briefs – “The Productivity Suites War” (at http://www.focus.com/briefs/information-technology/web-based-productivity-suites-war/) and “10 Signs that it May be Time to Consider a Web-based Productivity Suite” (at http://www.focus.com/briefs/information-technology/10-signs-it-may-be-time-consider-web-based-business-software/). And if you have opinions on where online collaboration and productivity suites are headed, please share them at http://www.focus.com/groups/information-technology/topics/view/officeproductivity-applications-desktop-cloud/.
Microsoft is in fact focusing largely on support for collaboration with its Office Web Applications. They’re accessible via Internet Explorer, Firefox or Apple’s Safari Web browser (but not Google’s Chrome, at least so far), and the Web-based version of Excel already supports multi-authoring, or simultaneous editing of the same workbook by multiple collaborators. Users can’t yet create Word documents, but should soon be able to create and collaborate on all types of Office documents.
Microsoft plans to make Office Web Applications available in three different modes. Subscribers to its Windows Live service will have no-cost access. Users of Microsoft Online Services will be able to purchase subscriptions. And companies licensing Microsoft Office 10 will also be able to license and provide access to Office Web Applications.
I expect these Microsoft offerings to be very popular, especially at companies seeking to reduce or halt the growth of their licensing and support contract costs for Microsoft Office. Many such companies have deployed or begun exploring other online alternatives from Adobe, Google, Zoho and elsewhere. However, these all offer mixed bags of interoperability and compatibility with native Office applications and file formats. So an online suite from Microsoft should eventually offer an alternative that does not suffer from such limitations. But those other online office/productivity suite providers aren’t going to stand still either.
Microsoft’s official entry into the online collaboration suite market will definitely make the market more interesting. Whether it will benefit Microsoft as much as or more than its cloud-based competitors remains to be seen. But where users are concerned, more online collaboration choice is definitely better, especially if it comes with more seamless interoperability with all of those Microsoft Office files most of us rely upon every day to do business.
If you want to know more, check out these two Focus Research Briefs – “The Productivity Suites War” (at http://www.focus.com/briefs/information-technology/web-based-productivity-suites-war/) and “10 Signs that it May be Time to Consider a Web-based Productivity Suite” (at http://www.focus.com/briefs/information-technology/10-signs-it-may-be-time-consider-web-based-business-software/). And if you have opinions on where online collaboration and productivity suites are headed, please share them at http://www.focus.com/groups/information-technology/topics/view/officeproductivity-applications-desktop-cloud/.
Tuesday, June 2, 2009
Google Wave: The Future of Collaboration, Unified Communications and Business Intelligence
Note: I originally posted this at ebizQ, but wanted to make sure everyone saw it here, too. If you've already read it, my apologies -- feel free to share with someone who hasn't!
Lars and Jens Rasmussen of Australia, the creators of Google Maps, have done it again.
Google Wave is an open platform and open set of application programming interfaces (APIs) that integrates multiple collaboration techniques into logical, flexible and powerful virtual shared conversations, or "waves." You can "jump in" at any point in a wave's existence, play back parts you missed, and determine whether everyone or only certain people receive whatever you decide to share. Waves can feed blogs with minimal coding. Web sites can be wave-enabled with relative ease. You can access and participate in waves from mobile devices. Waves enable consolidated content collaboration and discussion - no need to choose between, for example, an e-mail thread and a wiki.
There's a whole bunch of other cool stuff in Google Wave, but there's no way I could do it justice here - at least not until I download and become conversant with the APIs and relevant other tools. Which isn't happening - not this week, anyway. You should go to http://wave.google.com and check out the hour-plus presentation and demo, take a shorter "sneak peek" or learn more about the Wave.
And you should expect to be as surrounded by waves as Australia, Tasmania, or your ocean-based land mass. The growth of public, private and hybrid computing clouds is very likely to be mirrored by the growth of public, private and hybrid waves supporting every type of business communication, collaboration or relationship. Which means waves will quickly become essential tools in the service of those pursuing more and better business intelligence (BI).
Why am I so confident? Partly because of what's happened to and with Google Maps - zero to near-ubiquity as the enabler of geographic content and features in Web-based applications in almost no time. Partly because of what's happened and is happening to and with Google Docs & Apps. But mostly because of all of the above, plus it's Google. And because I can't imagine any type of size of business that can't improve communication, collaboration and/or outreach to clients, prospects and partners with the current and likely forthcoming features of Google Wave.
The open APIs and protocols, along with Google Wave's native HTML 5.0 foundations, mean that integration with other online and traditional applications is coming sooner rather than later. And I'm sure that tools for analysis of feature and content access and use patterns are also coming soon. Heck, someone's probably working on direct integration with at least one open source BI tool even as I write this, let alone by the time you read it.
Frankly, I'm hoping to encourage development of more features and integrations among all interested in Google Wave. I am fervently convinced that the delivery of customizable and flexible consolidations of content creation, collaboration and sharing can lead almost directly to greater BI - and more intelligent businesses. And Google has demonstrated its ability to develop and deliver powerful, flexible and open enabling technologies. So I, for one, expect a tsunami of support for Google Wave, and for must of that support to result in new and useful options for those seeking powerful and flexible BI solutions.
Lars and Jens Rasmussen of Australia, the creators of Google Maps, have done it again.
Google Wave is an open platform and open set of application programming interfaces (APIs) that integrates multiple collaboration techniques into logical, flexible and powerful virtual shared conversations, or "waves." You can "jump in" at any point in a wave's existence, play back parts you missed, and determine whether everyone or only certain people receive whatever you decide to share. Waves can feed blogs with minimal coding. Web sites can be wave-enabled with relative ease. You can access and participate in waves from mobile devices. Waves enable consolidated content collaboration and discussion - no need to choose between, for example, an e-mail thread and a wiki.
There's a whole bunch of other cool stuff in Google Wave, but there's no way I could do it justice here - at least not until I download and become conversant with the APIs and relevant other tools. Which isn't happening - not this week, anyway. You should go to http://wave.google.com and check out the hour-plus presentation and demo, take a shorter "sneak peek" or learn more about the Wave.
And you should expect to be as surrounded by waves as Australia, Tasmania, or your ocean-based land mass. The growth of public, private and hybrid computing clouds is very likely to be mirrored by the growth of public, private and hybrid waves supporting every type of business communication, collaboration or relationship. Which means waves will quickly become essential tools in the service of those pursuing more and better business intelligence (BI).
Why am I so confident? Partly because of what's happened to and with Google Maps - zero to near-ubiquity as the enabler of geographic content and features in Web-based applications in almost no time. Partly because of what's happened and is happening to and with Google Docs & Apps. But mostly because of all of the above, plus it's Google. And because I can't imagine any type of size of business that can't improve communication, collaboration and/or outreach to clients, prospects and partners with the current and likely forthcoming features of Google Wave.
The open APIs and protocols, along with Google Wave's native HTML 5.0 foundations, mean that integration with other online and traditional applications is coming sooner rather than later. And I'm sure that tools for analysis of feature and content access and use patterns are also coming soon. Heck, someone's probably working on direct integration with at least one open source BI tool even as I write this, let alone by the time you read it.
Frankly, I'm hoping to encourage development of more features and integrations among all interested in Google Wave. I am fervently convinced that the delivery of customizable and flexible consolidations of content creation, collaboration and sharing can lead almost directly to greater BI - and more intelligent businesses. And Google has demonstrated its ability to develop and deliver powerful, flexible and open enabling technologies. So I, for one, expect a tsunami of support for Google Wave, and for must of that support to result in new and useful options for those seeking powerful and flexible BI solutions.
Sunday, February 15, 2009
Twitter: Next Stop, Some "Tweet" Revenues?
Sitting on a $50-million cash reserve, how should Twitter generate revenues? Targeted ads like Google? Job ads like LinkedIn? Enterprise editions with private labeling, enhanced security, performance guarantees and service level agreement (SLA) support, and fee-based support? I'm just free-styling here, but they've got to do something, so what should it be? E-mail me at medortch@dortchonit.com, tweet me publicly or @dortchonit, and/or leave a comment here, and let's see if we're as clever as Twitter management or Twitter's investors.
Subscribe to:
Posts (Atom)