Building A Business Case For Digital Asset Management
-
Upload
giantsteps-media-technology-strategies -
Category
Technology
-
view
2.700 -
download
0
description
Transcript of Building A Business Case For Digital Asset Management
Slide 1
GiantStepsMedia Technology Strategies© 2009 1
Building a Business Casefor DAM
Bill RosenblattGiantSteps Media Technology Strategies
+1 212 956 [email protected]
Slide 2
GiantStepsMedia Technology Strategies© 2009 2
About GiantSteps
Consultancy focused on content technology strategy– DAM, content management– Workflow– Distribution– Rights management
In business since 2000
Clients include leading media and technology companies
Front-end strategy work– Independent of vendors, integrators
Slide 3
GiantStepsMedia Technology Strategies© 2009 3
Today’s Agenda
Sources of ROI for DAM
Scalable Product Methodology
Case Study
Slide 4
GiantStepsMedia Technology Strategies© 2009 4
Axes of ROI
Existing
OperationsNew Products & Services
Revenue
Cost Savings
Slide 5
GiantStepsMedia Technology Strategies© 2009 5
Cost Savings – Existing Operations
Pros– Quantifiable– Measurable– Attributable to management
Cons– Usually involves layoffs,
negative attitudes– Small magnitudes
Results– Hardly ever works in
commercial media environment
– May work in other industries with command-and-control culture
Slide 6
GiantStepsMedia Technology Strategies© 2009 6
Revenue – New Products & Services
Pros– Larger upside potential– Larger scope for investment– Growth, positive attitudes
Cons– Harder to quantify– Harder to tie results
specifically to DAM system– Harder to approve (part of
bigger picture)
Result– If used by itself, results in
small silos & point solutions
Slide 7
GiantStepsMedia Technology Strategies© 2009 7
Cost Avoidance(Cost Savings – New Products & Services)
Pros– Possibly quantifiable– Tied to revenue, so higher
scope for investment– Could be tied to “we’re doing
this anyway” new initiatives
Cons– Harder to tie results
specifically to DAM system– Harder to approve (part of
bigger picture)
Result– If used by itself, results in
small silos & point solutions
Slide 8
GiantStepsMedia Technology Strategies© 2009 8
The Third Axis:Single vs. Multiple Groups(Product groups, business units, etc.)
Single: – Lower cost– Easier to justify, approve, and implement– But usually results in non-scalable silo
Multiple: – Larger scope for investment– Justifies more scalability and features– But requires political planetary alignment
Slide 9
GiantStepsMedia Technology Strategies© 2009 9
The Ideal:Scalable Product Development
Base business case on revenue & cost avoidance in multiple new products and services– Not just currently known ones– Potential for future efforts yet to be defined
Platform for new product development with incremental cost– Avoid building silos for each new product/service– Cost savings for existing operations is icing on cake
Sea change in commercial content businesses – From one-brand-one-product to one-brand-many-products– Mindset that new product development is an ongoing thing, not a
one-shot project
Slide 10
GiantStepsMedia Technology Strategies© 2009 10
SPD Advantages
Business case based on upside, positive attitudes, not cost-cutting and personnel reduction
Scalable platform for growth, not point solution
Yet based on known business needs, not “build it and they will come”Scope for major investment with real impact
Process includes “a-ha moment” to accelerate buy-in
Slide 11
GiantStepsMedia Technology Strategies© 2009 11
SPD Business Case Methodology
1. Aggregate future initiatives
2. Identify common capability requirements
3. Create gap analysis
4. Synthesize requirements
5. Create implementation plan
6. Create project organization(s)
7. Identify first project and go!
Slide 12
GiantStepsMedia Technology Strategies© 2009 12
1. Aggregate Future Initiatives
Interview execs across product groups, business units, divisions, etc.– Typically strategy, marketing, business development
Gather info about future plans– Could range from specific plans to wish list items
Get them to be specific– Timelines– Priorities– Financial implications (e.g. revenue projections)
Interview IT dept. for info on existing systems, architecture– Resist “build it and they wil come” tendencies
Slide 13
GiantStepsMedia Technology Strategies© 2009 13
2. Identify Common Capability Requirements
Technical capabilities– Invariably includes DAM or other form of content
management
Processes to be implemented/improvedSkills to be acquiredOrg chart implicationsCommonality of themes often surprisingly large
– This is the “a-ha moment”– Makes it much easier to get buy-in
Slide 14
GiantStepsMedia Technology Strategies© 2009 14
3. Create Gap Analysis
What’s possible now?
What’s possible but too hard, inefficient, expensive?
What’s impossible now?
What has been tried before and rejected, and why?
Slide 15
GiantStepsMedia Technology Strategies© 2009 15
4. Synthesize Requirements
Usually flows naturally from gap analysis
Don’t worry yet about feasibility– Complexity– Cost– Risk
Slide 16
GiantStepsMedia Technology Strategies© 2009 16
5. Create Implementation Plan
Elements – Technologies– Process changes– Org chart changes– Training
Encapsulated into projects Prioritized
– Low hanging fruit first
Rough time and cost estimates– Formal ROIs will come later
2-3 year time horizon– Between annual operating plan and long-range strategic plan
Slide 17
GiantStepsMedia Technology Strategies© 2009 17
6. Create Project Organization
Steering Committee – Senior business line executives– High level oversight, fit to strategy
Working Group– Technical/process/production execs, 1-2 levels down– Nuts and bolts issues– Meet more often, report to Steering Committee
Slide 18
GiantStepsMedia Technology Strategies© 2009 18
7. Identify First Project
Most important criteria:– Strategic value to business– Time to impact– Implementation risk– Smooth political path
Less important:– Cost– Operational changes
(need some changes, otherwise why bother, and the earlier the better)
Now is the time to do formal ROI– If you even need it; benefits could be self-evident by this point
Slide 19
GiantStepsMedia Technology Strategies© 2009 19
Case Study: Associated Press
Largest and oldest newsgathering org in the world
4000 employees in 240 locations worldwide
Cooperative of 1500 daily newspapers
Produces text, photos, graphics, audio, video, and online content
Serves print, radio, TV, online, and corporate customers
Slide 20
GiantStepsMedia Technology Strategies© 2009 20
Problems to be Solved
Siloed systems for each media type– Text, photo, print graphics, video graphics, audio, video, and web– Limited ability to link content across media types by subject matter– Common denominator: ancient teletype-oriented system
Inefficient newsgathering/editorial processes– Difficulty in coordinating cross-bureau/desk newsgathering– Difficulty in communicating with members/affiliates about event
coverage
Various new product plans– Different feeds & aggregations of content
Slide 21
GiantStepsMedia Technology Strategies© 2009 21
Disparity of Requirements
Editorial: more efficiency, ease of communication
IT: integrated platforms, ease of future development and maintenance
Marketing/strategy: new product development, new revenue sources
Slide 22
GiantStepsMedia Technology Strategies© 2009 22
Methodology
Gather objectives across multiple axes:– Functional: editorial, marketing, IT– Media type: text, photo, video, audio, print graphics, video graphics– News units: bureaus (LA, Trenton,…), desks (national, business,…)
Examples:– Link objects of multiple media types by new event– Increase internal & affiliate visibility into ongoing coverage– Create custom news feeds by category to corporate customers– Feed content grouped by event to media customers (e.g., TV stations)– Design standard interfaces to/from disparate content systems
Slide 23
GiantStepsMedia Technology Strategies© 2009 23
Methodology
Observe systems, processes & workflow
Synthesize requirements
Present to combined groups– Enjoy the “a-ha moment”
Create gap analysis
Create list of technologies, processes, skills needed– Metadata creation as early as possible in newsgathering process
Create implementation plan
Slide 24
GiantStepsMedia Technology Strategies© 2009 24
Common Requirements Synthesized
Examples: Create metadata as early as possible
– Preferably during news assignment
Categorize content by keyword– Requires combination of technology and “library science” skills– Must not compromise reporters’ & editors’ ability to move content
onto the wires as quickly as possible
Create central metadata archive– Though link to content in existing, separate systems– Make it possible to search, browse, access content from single
interface (UI or API)
Slide 25
GiantStepsMedia Technology Strategies© 2009 25
Implementation Plan
First project: eAssign– Assignment tracking system– Metadata entry at assignment time
Next: eCentral– Central metadata archive
Various others
Slide 26
GiantStepsMedia Technology Strategies© 2009 26
Successes
Got various groups together that had previously little interaction
Found surprising amount of commonality, even among seemingly conflicting goals
Agreed on cross-functional architecture elements
Enabled investment in enterprise platform for growth instead of silos and point solutions
Eliminated the need for much arduous ROI analysis –management “got it”
Slide 27
GiantStepsMedia Technology Strategies© 2009 27
Case Study: Mass. Medical Society
Journal Watch – summaries of medical journals, daily news updates, continuing medical education
Print, online, and audio products
Monthly and daily “breaking news”Large body of outside contributors/editors
Slide 28
GiantStepsMedia Technology Strategies© 2009 28
Problems to Be Solved
Large number of outside contributors– Communication with internal editors– Workflow
MS Word-based publishing process
Print first, online later– Laborious conversion process
Multiple non-scalable content/metadata repositories– XML at the end of the line
Plans for various new online offerings– Increasing competition
Slide 29
GiantStepsMedia Technology Strategies© 2009 29
Methodology
Gather objectives across multiple axes:– Functional: editorial, marketing, IT– Content type: text, audio, breaking news, longer-term– Medical practice areas (dermatology, infectious diseases, etc.)
Examples:– Increase collaboration among outside and internal people– Eliminate overlapping coverage– Enable more user generated content on website– Streamline editorial processes;
fewer “hands” but same editorial quality– Direct-to-online path for time sensitive content– Support migration to new web CMS
Slide 30
GiantStepsMedia Technology Strategies© 2009 30
Methodology
Observe systems, processes & workflow
Synthesize requirements
Present to combined groups– Enjoy the “a-ha moment”
Create gap analysis
Create list of technologies, processes, skills needed– Metadata creation as early as possible in newsgathering process
Create implementation plan
Slide 31
GiantStepsMedia Technology Strategies© 2009 31
Common Requirements Synthesized
Examples: Create metadata as early as possible
– Create Assignment Desk for this purpose
Categorize content by keyword– Requires combination of technology and “library science” skills– Must not compromise reporters’ & editors’ ability to move content
onto the wires as quickly as possible
Create central XML repository– Produce XML earlier in editorial process– Direct feed from repository to web CMS
Slide 32
GiantStepsMedia Technology Strategies© 2009 32
Implementation Plan
New staff/management roles
Streamlining of processes into three areas:– Content creation– Product creation– Product delivery
Set up Assignment Desk– Adopt collaboration tools
Adopt new DAM tools
Implement new workflows
Transition to new web CMS
Slide 33
GiantStepsMedia Technology Strategies© 2009 33
Successes(Same!)
Got various groups together that had previously little interaction
Found surprising amount of commonality, even among seemingly conflicting goals
Agreed on cross-functional architecture elements
Enabled investment in enterprise platform for growth instead of silos and point solutions
Eliminated the need for much arduous ROI analysis –management “got it”
Slide 34
GiantStepsMedia Technology Strategies© 2009 34
Bill RosenblattGiantSteps Media Technology Strategies
+1 212 956 [email protected]