We provide templates for vendor evaluations, can help write and review your user stories, and are happy to participate in tool evaluations that integrate with other applications or intersect with multiple departments.
Please involve us in all tool evaluations that integrate into the enterprise application ecosystem before beginning demos with vendors.
What are the BSAs working on?
Business Analysis Support
Phil Encarnacion, Business Systems Specialist
Barbara Roncato, Business Systems Analyst
Works with the Finance and Accounting teams to improve workflows, processes, and application ecosystem
Project work to implement new modules to tools
Works with stakeholders from other teams like Field Ops and Fulfillment team that integration with the financial ecosystem.
Works closely with Finance Systems Administrator
Portal integrations and operations
Jamie Carey, Senior Business Systems Analyst
Portal Analysis and Documentation
Works closely with Go to Market Operations (Marketing and Field Ops), Customer Success Operations, and Channel Operations.
Security and Compliance
Karlia Kue, Business Systems Analyst
Works closely with the Legal and Security teams to ensure business compliance
Business Preparedness Plans
IT Operations and People Operations
Lis Vinueza, Business Systems Analyst
Works closely with IT Operations and People Operations
Automation of system provisioning
Business Operations and Workflows
Embed Tech stack in Handbook
Tech Stack: Maintenance
Zendesk <> SFDC integration
What does a BSA do?
Note: BSA team needs to create templates for the types of work below
vendor score cards
BSAs start by asking questions about the current state of a process, integration, or tool evaluation in order to understand what the pain points are for the people involved.
Often this is research that takes interviews of subject matter experts, reading existing documentation, and requesting confirmation of what they are learning as they tie existing information into the rough draft documentation of the current state in new documents and diagrams.
BSAs also reach out to external vendors to request clarity, roadmap information, and support from account managers, product managers, and support teams.
scope (identification of edge cases), analysis, options
general project information: directly responsible individual, cost, vendors details
risks and benefits of design choices
project organization; communication, documentation, and training plans; escalation path, go-live criteria; meeting notes/recordings
schedule, status, and milestones achieved
change management plan
requirements (includes security, legal, and financial requirements)