Lisa Welchman

Managing Chaos


Скачать книгу

Editorial The style of language and the strategy for content delivery and curation. Branding (tone, use of company name, use of product names) Language (style manual/dictionary, terminology, cultural competence) Localization (translation, management, cultural adaptation) Publishing and Development Information management, development protocols, and publishing and infrastructure tools that impact the architectural aspects of information organization and delivery. Information Organization and Access (information architecture, taxonomy, metadata, file-naming conventions, Web records management, accessibility) Tools (portal, Web content management, search, translation management, document management, collaboration, digital asset management, surveying, webcasts, social software, Web analytics, usability) Development Protocols (RSS links and specifications, multimedia, operating systems, browser compatibility, browser detection, load time, single sign-on, mobile, password management, FTP, frames, personal data collection, code, file types, cookies and sign-in, personal data retention, non-HTML content) Network and Server The platform-focused aspects of digital production. Domains (domain format/names, use of domain name, domain name redirects, vanity/marketing domains) Hosting (site backup, disaster recovery, supported connection speed, personal data retention) Security (personally identifiable information, ebusiness/financial transactions, security protocols to protect information, visitor data and traceability, firewall rules, data safety and transmission intrusion detection, alerting mechanism, monitoring mechanism SSL, passwords, time-outs and auto log-offs) Server Software (databases, DB naming conventions, app server, Web server, virtual private network [VPN], operating system, domain name server, load balancer, file server, maintaining licensing keys, single sign-on, server analytics, wireless application protocol [WAP], maintaining warranties and servicing) Server Hardware (standard Web server configuration, database, app server, Web server, firewall appliance, maintaining warranties and servicing, test servers, caching)

      Rest assured—every organization has digital governance problems. Just because an organization might look good online doesn’t mean that it is getting a good return on its investment or operating in an effective, low-risk environment. I’ve seen plenty of “lipstick-on-pig” digital environments where a nice-looking website design was only thinly veiling an ineffective digital presence supported by no real digital strategy and an uncoordinated digital team—governance gone wild! I’ve also seen some “looks like it was built in 1997” websites where the site was getting real work done for the organization, and the supporting organization was only inches away from governing well. Looks can be deceiving.

      How can you tell how well your organization is doing? Instead of looking at your (and your competitor’s) websites, social channels, and mobile apps to judge how well you are governing, you can understand where you are on the digital governance maturity curve (see Table 1.3).

      You’ll probably find that your organization is at different levels of maturity for different aspects of the framework (team structure, digital strategy, digital policy, and digital standards). That’s normal. Maybe you work in a heavily regulated industry, and you’re “mature” when it comes to digital policy, but you lack standards. Or maybe you have some policy and standards, but you have no real digital strategy. The point is for you to assign responsibility and accountability to the right set of resources so that the substance of your strategy, policies, and standards is on target, laying the foundation for your digital team to create real online value for the organization.

      Once you’ve finished designing your framework, you will find that accountability and authority for strategy, policy, and standards will be distributed throughout your organization’s digital team. But do you know who your digital team is and what they do? Maybe not. So before we examine how to determine accountability for each of the digital governance components, let’s take a look at how digital teams are structured. Just as websites grow organically and without much of a plan, so do digital teams. It’s important to take the time to establish and put into place a well-defined digital team before you begin your governance design efforts.

       Understanding Digital Governance Maturity

      There is a digital governance maturity curve (see Figure 1.6) that most organizations move through when they launch a digital channel (Web, mobile, or social). The process of maturity begins with the decision to launch a new channel, and it culminates with the organization having fully integrated that channel into the company to the extent that governing dynamics and operational processes are automatic, leaving the organization fully responsive to digital trends.

      The dynamics of each phase are fairly distinct. Most organizations that are seeking to improve digital governance are usually in the “chaos” phase, while some are stalled at “basic management” and trying to move to the next level. Also, organizations are typically at different places on this curve, depending on which digital channel is being considered. For example, an organization might be at “basic management” for websites, but at “launch” for its mobile channel, while in “chaos” for social channels. This issue can add complexity when designing a digital governance framework.

image

       GOVERNANCE AND DIGITAL ANALYTICS

image

       Phil Kemelor, EY

       In my work with Fortune 500 companies, government agencies, and national non-profit organizations, the linkage between smart Web governance and intelligent use of analytics data goes hand-in-hand. Governance sets the tone for a culture of analytics through clear definition of strategy and direction as to what metrics and measurement guide accountability in achieving goals related to the strategy.

Maturity Stage Dynamics
Launch Research and development mode, as the digital functionality or channel is being informally tested or formally piloted.
Basic policy constraints are considered to ensure that the organization is operating within the bounds of the law and any other regulatory constraints.
There are few standards imposed at this point because the organization is just going to “try out” new functionality to see if there is value to the organization.
Organic Growth Aspects of functionality “work.” Others in the organization begin to leverage the work of the piloting team.
Functional and systemic redundancy