140 likes | 246 Views
Backend Publishing Systems Team January 27, 2004. Contents. Opening Remarks Goal Discussion Why a CFT Importance of Backend Publishing System Options/Strategies Tactics How will the CFT operate Process Decision Making Communication Implementation of Decisions
E N D
Backend Publishing Systems Team January 27, 2004
Contents • Opening Remarks • Goal Discussion • Why a CFT • Importance of Backend Publishing System • Options/Strategies • Tactics • How will the CFT operate • Process • Decision Making • Communication • Implementation of Decisions • Roles and Responsibilities • Discussion of Options in the context of Goals/Strategy,Timing, and Tracks • Summary, Next Steps
Goals • Defining the Goal • What we need to do • Why we need to do it • When it needs to be done • How: constraints and enablers
Why This Approach? • Aligning company goals and objectives with department and individual activities • Execute around company priorities • Cross-functional communication • Cross-pollination of understanding company, department, and staff operations • Manage staff more effectively • Build into daily activity more efficiency, effectiveness and productivity • Streamline workload and reduce the common waste of time, money, people, and material resources • Identify bottlenecks, constraints, capability gaps and ways to redirect the current approach • Gets the job done on time, on target, on budget
Why a CFT? • Importance of Backend Publishing System • $4 million in 2004 • Core business • Tool effects sales, production, analysis, BD, etc. • Strategy • Evaluate options in context of tracks • Tactics • Implement strategies for different tracks
How will the CFT operate • Characteristics • Goal oriented, defined Structure, and defined Roles and Responsibilities • Process • Weekly meeting to: • Review action items and timeline • Discuss disconnects and alignment with corporate goals • Decision Making • Group based based on best interests of company • CFT Chair will resolve conflicts and make decision if necessary • Communication • Open and direct: weekly meeting minutes, project plan, email, 1v1 and group discussions as needed • Implementation • Aggressive project approach • Tasks assigned and dependencies understood • Proactive identification of slippage and swift identification of alternatives
Roles and Responsibilities • Account Management • Analysis Business Development • Customer Service • Finance - TBD • HR • IT • Marketing • Sales • Production
Discussion, Next Steps • What we need: • Draft statement of roles and responsibilities to team • Due by Friday 1/30/04 to Ron by All • Requirements for Backend Publishing System from each functional area • Due by Friday 2/6/04 to Mike by All • Gap analysis on requirements and what we currently to set stage for actions • Due by Monday 2/9/04 to All by Mike