Time Entry Transformation
Welcome to the Time Entry Transformation project website, your central hub for staying informed about the transformation. Here, you can access the latest updates, track the project timeline, and sign up to receive email updates through a subscription to GovDelivery. Explore our resources, including answers to frequently asked questions, key dates, and information on who's listening to your feedback. Whether you have questions or want to stay up to date, this site is designed to keep you connected and engaged with the project.
Welcome to the Time Entry Transformation project website, your central hub for staying informed about the transformation. Here, you can access the latest updates, track the project timeline, and sign up to receive email updates through a subscription to GovDelivery. Explore our resources, including answers to frequently asked questions, key dates, and information on who's listening to your feedback. Whether you have questions or want to stay up to date, this site is designed to keep you connected and engaged with the project.
-
Sprint Review 5
Share Sprint Review 5 on Facebook Share Sprint Review 5 on Twitter Share Sprint Review 5 on Linkedin Email Sprint Review 5 linkSprint 5 Goal (5/21/25 – 6/3/25):
•Focus on getting all MVP1 work to the QA environment. Finalize decision from ICAM for Oath, Entra, and Multi-Factor authentication. Get domains set up.
•Actual: Did not accomplish our goal but did make major progress on the front end, authentication is being escalated through management and our final domain name is being reviewed with communications.
-
Sprint Wins Spring 2025
Share Sprint Wins Spring 2025 on Facebook Share Sprint Wins Spring 2025 on Twitter Share Sprint Wins Spring 2025 on Linkedin Email Sprint Wins Spring 2025 linkSprint Wins 2025
- CCM TET backlog organized with plans and timelines.
- All team members can record their own work and set up for scrum workflow processes with sprints.
- Project charter draft completed and under review.
- Project kick-off meeting with legal and additional consult lined up.
- Created team norms for conduct and communication with fully onboarded product team.
- New group email address set up for SSIS User Acceptance Testing {UAT) with TET.
- Presented early findings with user research, mobile design, and Minimum Viable Product (MVP) definition to key leadership team members.
- CCM TET backlog workflow in place and finalized by team.
- Project charter reviewed and approved by project sponsors.
- Held a follow-up meeting with legal on log-in screen disclaimer and warning messages.
- Worked on our product roadmap as a team.
- Presented to the TCM Systems Changes county-led workgroup on 5/28/25 with an update on EHQ, surveys, and a design to development walk-through.
- Closed Contact/Activity screen survey as of 5/30/2025, received 267 responses.
-
Sprint Review 4
Share Sprint Review 4 on Facebook Share Sprint Review 4 on Twitter Share Sprint Review 4 on Linkedin Email Sprint Review 4 linkOur sprint reviews are held internally with our key partners, and we want to share our progress with all of you as we kick off development work and build together with local agency workers.
Sprint 4 Progress (5/7/25 - 5/20/25):
Deliver critical security and design decisions by remediating authentication risks, establish stable UAT and QA environments, implement the foundational UI design including the landing page, and enable users to create a new time record via the front-end, ready for functional and usability testing.
Sprint 5 Goal (5/21/25 - 6/3/25):
ICAM for Oath, Entra, and Multi-Factor authentication. Get domains set up .
Focus on getting all MVP work to the QA environment. Finalize decisions.
-
Sprint Review 3
Share Sprint Review 3 on Facebook Share Sprint Review 3 on Twitter Share Sprint Review 3 on Linkedin Email Sprint Review 3 linkSprint 3 Review (4/23/25 - 5/6/25)
Thank you for reading our Sprint 3 review for the Time Entry Transformation web application! This new tool is being developed to give county and Tribal Nation case workers mobile access to enter time records-an improvement to access that will work alongside the current desktop SSIS system. During this sprint, we focused on finalizing key authentication and security components, defining what our first version minimum viable product (MVPl) will include, and welcoming a new front-end developer to the team, allowing us to move forward with full development support. MVPl will allow users to create new time records on mobile or desktop, with responsive design and better accessibility. We're also aiming for a smoother login process, reduced lag, and improved system stability.
Looking ahead to Sprint 4, we're focused on setting up stable testing environments and building the main user interface, including a new landing page. We'll also start preparing the app for usability and functional testing, including user acceptance testing (UAT) with a small group of local agency users. Interested In helping us test and pilot the new contact activity recording solution? Sign up through this link! Training materials will begin rolling out ahead of our targeted MVP release in Summer 2025. Feedback from users continues to guide our decisions, and we welcome your thoughts throughout this process. We hope to have frontend development updates to show everyone in the coming sprints as our team moves from the crawl to walk phase in our Crawl-Walk-Run approach.
Current SSIS Contact/ Activity Screen --> Low-Fidelity Prototype for New Activity/Time Entry --> Developed Mobile New Time Entry
-
Sprint Review 2
Share Sprint Review 2 on Facebook Share Sprint Review 2 on Twitter Share Sprint Review 2 on Linkedin Email Sprint Review 2 linkOur sprint reviews are held internally with our key partners, and we want to share our progress with all of you as we kick off development work and build together with local agency workers.
Sprint 2 Plans (4/9/25 – 4/22/25)
The sprint focused on:
Adding a project manager/scrum master team member to help with resource alignment and capacity planning.
Further development discoveries to refine the Minimum Viable Product (MVP).
Enhancing authentication & security solutions for user protection.
User-centered design improvements based on caseworker feedback.
Statewide feedback gathering on service activities & mobile use.
Launching surveys to broaden participation in design decisions.
Roadmap & Key Milestones
The planned feature rollout includes:
Summer 2025: First MVP release, allowing case workers to enter new time records via the web-based system that integrates with the existing SSIS application and databases.
Multi-factor authentication will likely be introduced for secure access, exploring options for password reset and forgot username.
User Input & Engagement
The team emphasizes user-driven design, actively seeking feedback through:
Meetings, chat discussions, and direct outreach with key partners and local agency workers.
Service activity code review using a Mural Board.
Qualtrics survey on mobile use and device availability to collect further feedback.
Key Takeaway
This product is designed with case workers in mind, making time entry simpler, mobile-friendly, and more efficient. The team values user input and is working toward a modernized solution that meets real-world needs. By reducing time spent on system inputs, workers can spend more time directly serving children and families.
-
TET Sprint Review Update
Share TET Sprint Review Update on Facebook Share TET Sprint Review Update on Twitter Share TET Sprint Review Update on Linkedin Email TET Sprint Review Update linkSprint Reviews Update
The Time Entry Transformation Product is designed to improve how case workers enter their time in the Social Services Information System (SSIS). The transition is necessary due to upcoming federal changes, requiring time tracking in 15-minute increments rather than the current bundled monthly rate.
To support this shift, the team is developing a web-based, mobile-friendly application that will:
Enhance system reliability & performance to ensure stability.
Increase caseworker efficiency by reducing clicks and automating routine tasks.
Improve user experience & adoption through user feedback-driven design.
Development Progress & Sprint Reviews
This effort will work with agile methodology and scrum framework in two-week iterations that began on 2/26/25.
We honor the scrum ceremonies of the daily stand-up, sprint planning, product backlog refinement, sprint retrospectives, and sprint reviews.
Our sprint reviews are held internally with our key partners, and we want to share our progress with all of you as we kick off development work and build together with local agency workers.
Sprint 0 (2/26/25 – 3/11/25)
The team assembled and planned the initial product roadmap. The focus was on:
Understanding user needs and gathering feedback.
Defining the product backlog for future development.
Setting up Agile methodologies within a scrum framework, including structured work cycles (sprints).
Sprint 0.5 (3/12/25 – 3/25/25)
Progress included:
Adding a quality assurance (QA) team member to enhance development oversight.
Determining login & authentication processes to ensure secure database access.
Creating wireframes for users to interact with and provide feedback.
Meeting with county workgroups to refine case worker service activity options.
Developing job aids to assist workers with new reporting requirements.
Sprint 1 (3/26/25 – 4/8/25)
The first official development sprint focused on:
Completing login & authentication setup for secure access.
Testing wireframes with users and gathering insights for improvement.
Engaging county workgroups to further refine service activities and reporting needs.
Sprint 2 Plans (4/9/25 – 4/22/25)
The sprint focused on:
Adding a project manager/scrum master team member to help with resource alignment and capacity planning.
Further development discoveries to refine the Minimum Viable Product (MVP).
Enhancing authentication & security solutions for user protection.
User-centered design improvements based on caseworker feedback.
Statewide feedback gathering on service activities & mobile use.
Launching surveys to broaden participation in design decisions.
Roadmap & Key Milestones
The planned feature rollout includes:
Summer 2025: First MVP release, allowing case workers to enter new time records via the web-based system that integrates with the existing SSIS application and databases.
Multi-factor authentication will likely be introduced for secure access, exploring options for password reset and forgot username.
User Input & Engagement
The team emphasizes user-driven design, actively seeking feedback through:
Meetings, chat discussions, and direct outreach with key partners and local agency workers.
Service activity code review using a Mural Board.
Qualtrics survey on mobile use and device availability to collect further feedback.
Key Takeaway
This product is designed with case workers in mind, making time entry simpler, mobile-friendly, and more efficient. The team values user input and is working toward a modernized solution that meets real-world needs. By reducing time spent on system inputs, workers can spend more time directly serving children and families.
-
TET Product Update
Share TET Product Update on Facebook Share TET Product Update on Twitter Share TET Product Update on Linkedin Email TET Product Update linkThe TET (Time Entry Transformation) product team is focused on improving the digital experience for county workers using SSIS by building with them and not for them. Our team has conducted interviews and surveys to identify key challenges and opportunities for improvement. Some of the main issues include a cumbersome system interface, technical reliability, data entry accuracy, and the need for mobile access.
We're developing a mobile tool for time entry that aims to reduce system interaction time and increase face-to-face time with clients. The prototype is a responsive single-page web app designed for use on mobile phones, tablets, and laptops. Initial key features include improved accessibility and stability, and mobile access. We hope to iterate and include more features in the future, like offline access and draft entries.
Feedback from agency workers has been positive and has highlighted the potential for increased efficiency and more accurate notetaking in the field. We are committed to continuing to build this new product with workers to ensure it meets their needs and enhances their daily workflows.
Stay tuned for more updates and opportunities to provide feedback as we continue to refine and develop this product.
-
SSIS Digital Experience Early Findings
Share SSIS Digital Experience Early Findings on Facebook Share SSIS Digital Experience Early Findings on Twitter Share SSIS Digital Experience Early Findings on Linkedin Email SSIS Digital Experience Early Findings linkThe Transformation team is thankful for those who have been able to participate in our data gathering opportunities. We continue to learn more about the SSIS user experience and look forward to providing more opportunities for feedback.
Below is a summary of our engagement process so far and what we have learned.
Quick Facts
Primary and Secondary data gathering methods to date:
- SSIS end-user digital experience interviews
- Mobile needs end-user survey
- Mobile contact activity tracking and time entry tool prototype reviews with case workers
Agency workers challenges and insights so far
System performance and reliability
Slow and cumbersome system interface
Frequent technical issues and low system reliability
Data entry and workflow efficiency
Poor accuracy and unnecessary data entry/duplication across various worker roles
Cumbersome case management regarding access to the most relevant information across worker roles
Workload requirements for case noting and time tracking across the various worker roles
Lack of intelligent system features
Lack of pro-active, useful alerts and reminders across worker roles to indicate when specific work is due
Mobile access limitations
Lack of mobile tools access and flexibility for workers who spend the majority of their time with families and away from their computers
Training and support gaps
SSIS training and support gaps across the various worker roles
Data access and integration issues
The necessity to access case data found across multiple, separate state and local data systems
Digital experience questions and themes
Questions asked about mobile usage, usability of SSIS, how individuals access information and their level of satisfaction.
The following themes came back as topics of importance:
1. Usability & efficiency of SSIS
2. Mobile access & field use
3. Voice-to-text & automation
4. Connectivity issues
5. Device concerns
6. Time-saving features
7. Data entry workflow
Early findings summary
Shared technical challenges, role-specific impacts
While technical challenges with SSIS are widely shared across agencies, the user interface (UI) impacts workers differently based on their roles. Despite these differences, all users face efficiency barriers in case data entry and management.One-size-fits-all interface creates confusion
Currently, SSIS uses a one-size-fits-all approach to data entry screens. This results in confusion, errors, and misalignment, as screens and fields are not tailored to the unique needs of different case worker roles.Need for role-based customization
Customizing the SSIS UI by worker role would significantly improve efficiency. Role-based customization would reduce redundancy, lower administrative burden, minimize confusion, and decrease the number of clicks needed to complete tasks. The time saved could be redirected to critical family casework.Research needed to guide modernization
To support these improvements, further research is needed to understand the specific data entry and management needs of individual worker roles. These insights should guide ongoing SSIS UX/UI modernization efforts to enhance efficiency for both state and local agency partners.Contact activity and time tracking mobile-ready tool
Primary users: Field-based caseworkers
Data shows that caseworkers who spend most of their time in the field are the primary users for a mobile-ready tool. These workers need a solution that allows them to efficiently enter contact activity notes and time records while away from a desktop or laptop.Secondary users: Desktop-based workers facing SSIS challenges
Caseworkers who primarily use desktop or laptop computers—and who face the broader SSIS challenges—are secondary users. They would also benefit from a mobile-ready solution adapted for desktop use, offering improved efficiency for contact activity and time entry.Words that shape design
Input from case workers who participated in the feedback opportunities held to date:
Need for mobile access in the field
“Right now I am unable to do notes into SSIS in the field. It is not convenient.”
“Being able to access SSIS in the field from phone would be great!!”
“SSIS is the ONLY reason I need a laptop. Everything else I do I can do from my cell phone. It is one of the biggest annoyances of my job! When I am supervising visits for families, being able to capture the information as it is happening would save me time, would be more efficient, and would result in more comprehensive notes.”
“This [mobile-ready] option would be valuable so the contact can be entered in real time which would provide a more detailed/accurate note.”
Frustrations with SSIS performance
“SSIS takes a long time to load, is not very user friendly, and crashes often whether in the office or in the field. If it crashed less often or moved more quickly it would be easier to get notes completed.”
“It is much more important to me that SSIS works, doesn't lag, doesn't take up to 5 minutes to look up an address or get data as SSIS is just spinning.”
“Rural area—we sometimes lose network at times, and some houses also have a loose network.”
Workarounds due to system limitations
“I currently enter notes in Outlook and then move them over to SSIS.”
“I typically type my contact/activity in Word due to SSIS closing unexpectedly and not saving contacts and because SSIS doesn't keep up with my typing speed. It would be helpful if these issues did not exist so that I could work directly in SSIS.”
Suggestions for usability and workflow improvements
“If the process were easier then I would use it. I think that this could be a very useful tool for workers. I think that this could help with workers getting SSIS notes into the system in a more timely manner.”
“It would be nice if SSIS could default to a service based on the workgroup, that could be editable if needed. It would be one less click.”
“Many of the buttons/clicking needed is redundant.”
“Must have easy interface. Click drop-downs and minimal typing is helpful. Common drop-downs populate for the service.”
“User-friendly app, easy to navigate and will allow you to correct errors, as needed.”
Opportunities for innovation
“Mobile connection with voice dictation could be a game changer.”
-
Transforming Our SSIS Time Entry System Together
Share Transforming Our SSIS Time Entry System Together on Facebook Share Transforming Our SSIS Time Entry System Together on Twitter Share Transforming Our SSIS Time Entry System Together on Linkedin Email Transforming Our SSIS Time Entry System Together linkWe are embarking on a transformative journey to reimagine how SSIS contacts and activities are recorded. At this moment, we are in the discovery phase- a critical first step where we prioritize understanding your experiences, challenges, and needs. Our commitment is clear: we will design this solution with you, not for you.
This means:
- Active collaboration throughout the entire process
- Listening to your insights and perspectives
- Ensuring the new system genuinely serves those who use it daily
We recognize that meaningful change starts with genuine partnership. Your expertise as Tribal and county workers, technical specialists, and community advocates is our most valuable resource.
We want to learn:
- What works well in the current system
- What creates obstacles in your daily work
- What innovations could dramatically improve your ability to serve Minnesota's families
In the coming weeks, we'll be reaching out through:
- Focus groups
- Surveys
- One-on-one conversations
- Collaborative design workshops
Sprint Review and Usability Updates
Custom
Who's Listening
-
CCWIS Modernization Supervisor
-
Fiscal Subject Matter Expert
Project Timeline
-
February → March 2025
-
March → April 2025
-
May → July 2025
-
August → September 2025
-
September → October 2025
News Categories
- #Sprint Review #Update (5)
- #SprintWins (1)