Identity Management Success

So you have finally passed all of the internal gate reviews, justification meetings, ROI calculations, evaluations, Proof of Concept phases (POC), budget reviews, training, and socialization, project planning, etc. — now it is time to implement.

There are many factors to consider when planning your kickoff meeting. In our opinion, here are the Top 10:

1. Marshall your resources, and get them all in the same place.

Identity projects are a fluid, yet tightly integrated series of actions between vendors, partners, and internal subject matter experts. Get everyone together — preferably offsite when possible — and review all of the primary project documents, including:

• Communications Plan
• Project Plan
• Deployment Plan
• Support Plan
• Maintenance Plan
• Integration Plan
• “To Be” Workflows (Describe how things will now be done after IDMS implementation)

Yes - kickoff meetings, and one could argue the same holds true for all serious kickoff meetings - should be conducted offsite. It is imperative that meetings are distraction free, and tightly focused. All kickoff team members must walk out of this meeting on the same page.

2. Ensure all purchase orders (PO) are fulfilled down to the last part, license and bolt.

It is surprisingly common to miss something in fulfillment. A vendor may ship the wrong part in a long list of components, the wrong version of software may be licensed, or multiple items may ship at multiple times, from multiple locations.

3. Keep the Audience List Tight.

People in the organization will be tempted by curiosity, or “managerial suggestion” to attend the kickoff sessions. If this may be a political issue in your organization, consider conducting a separate breakout session with an open forum.

4. Review the project timetables and budget.

Timetables and priorities are constantly changing within all organizations. At the Kickoff Meeting, your Identity Project is not yet past the point of no return. Take the time, discuss all of the deliverables, and get buy off from your vendor and internal subject matter experts (SME) that deliverables, milestones, and corresponding task lists are achievable and accurate. Adjust as necessary until the plan is seen as rock solid.

5. Review the proposed architecture from end to end.

See point # 5 above and apply it here. Remember: no matter how much time you spent in design prior to the Kickoff Meeting, you have not yet built it. The Kickoff Meeting is the perfect time to review the architecture picture by picture, connection by connection. If it makes sense to modify something, then do it. Ensure that you are deploying the IDMS with the most up-to-date information available.

6. Break technical and project teams into breakout sessions.

Server people need sessions with network people, the software people need sessions with the operating system people, analysts need sessions with the software people, etc. Treat your Kickoff like a big 1 - 3 day seminar. Alternate between group/global meetings, and tightly focused meetings with specialists and technical staff.

7. Record the meetings.

Let us be honest - in frenzied discussions among large groups of people, accurate scribing is almost impossible. Not only that, whomever is doing the scribing is having to focus on the raw content than the greater meaning and contributing to the discussion. Record and review later. Do not be afraid to deliver more cutting edge methods such as Podcasts or streaming audio to get the minutes out.

8. Go straight from Kickoff to Physical Implementation.

Momentum is key, especially if it has taken a long time to get to the Kickoff. Keep momentum going while the information is fresh, and the team is strong.

9. Have presentations ready for each major session, and each breakout session.

Encourage active discussion, but not ad hoc. Each session should have a clear set of bullets to cover. Start each session with a short deck of 3 - 5 slides describing the purpose. Go back to the slide 10 minutes before session end and ensure that everything has been covered.

10. Have fun!

Identity Management Programs are can be big and challenging. Focus on the endgame, but have fun in the process. Maintain active discussion and communicate frequently. Schedule team lunches or dinners after key milestones.