J C Walker Concepts
Example of Tangible Outputs
-
Tangible outputs: I am skilled in providing documentation to compliments each phase of an implementation. I provide the industry standard document outputs such as;
Configuration workbook [Excel]
This is holds specific data sets, such as Job Posting Catalogue, [job titles], Cost Objects, Business unit, Sites. The users operating the VMS e.g. the Hiring managers. And several more configuration details that allow any consultant in the industry to configure Fieldglass based on this workbook. Hhhhmmm, is there a standard set up that will make configuration easier?…well, yes… a good Fieldglass consultant will have in their minds eye, the base set up whilst asking questions during design workshops to ensure the basic set up will work for this client and make any adaptions necessary to suit their clients needs.
Configuration requirements document [Word & Visio]
Visio style workflow with narrative of the process. The narratives are call outs on specific goals of the program, including write up the because statement. The because statement will keep everyone accountable to why part of the process has been designed, and potentially help you evolve and refine the process in future.
-
E.g. all Job postings go via the HR business partner for the regions. Because. The HR business partner in the country has become aware through anecdotal observations of Contingent workers that roles are going out to market, when there is available resource in other departments. Now we know the because statement. The VMS consultant can approach the solution in a couple of ways. 1) all job posting go to HR business partner for approval. OR 2) HR business partner gets a report every week with all roles that have gone out to market and then challenge after the fact. Both are valid solutions, having the because statement means that if having the HR BP in the approval chain becomes blocker to onboarding contingent worker to meet the needs of the business, then the decision to have HR BP in approval process could be removed once they are satisfied that hiring managers is raise Job Posting only when necessary to meet the needs of the business.
Integration requirement document [Word]
This document holds the specific connectors and field mapping. In addition, I also add a table for any custom features, which are configurations that can only be completed by internal Fieldglass teams by raising a ticket. The secret sauce is knowing the options on when this can be achieved and how to ask. These custom feature configurations are where I have achieved success in the past, by getting the file from Fieldglass to produce the data with the content and format needed for the recipient application.