I'm not sure how much this will help, but I'll share what we do. We take a slightly different approach because of our structure. We don't allow end-users to decide that something should be a process flow - we ask them to tell us what data they need or what they are trying to accomplish, and our HCM Analysts have a sort of decision tree they use to decide what tool makes sense. We have an e-form for end user "data requests" that an end-user completes with basic information and submits to HCM Business Analyst team. Here is the text of that form: Please complete the following questions in as much detail as possible. This information will be reviewed by the HCM Application Analysts to determine the best tool necessary to deliver a solution. Tool sets may include Smart Notes, Crystal Reporting, Process Flow, Add-ins, Lawson Spreadsheet Designer or etc. Every request will be evaluated based on HCM and Business strategic direction. Some requests may go to the governance team to ensure consistency with standards.
1) Recommended Title:
2) Business Process Owner:
3) Requested By:
4) Describe the Problem:
5) Who needs to be notified or have access to the data?
(i.e. individual person, Footprints ticket, Distribution list, etc)
6) Who needs to be cc’d?
7) How often do you anticipate being notified or using this information?
8) Is an automatic update needed to the database? If yes, what needs to be updated?
9) Is an approval process required? If yes, please provide examples?
10) Which database stores the information?
11) Date needed?
The appropriate Analyst on that team uses the data on the form to determine the following:
Once the Analyst reviews the request and determines that development is required, then they meet with the end-user to get the additional information they need to develop a real functional spec document for the Developer and the Analyst puts that document together with the help of the end user. I hope this is somewhat helpful. Good Luck!