Closed CSwartzHMA closed 4 years ago
Team discussion today included a reference to the tables which use the term "In House Costs" as a collective description when state staff costs and other state expenses are combined. One possible way to bridge this concept is to rename the "State Cost Categories" page to "In-House Costs (State Staff + Other State Expenses)".
@CSwartzHMA I was thinking back to our debrief yesterday and our thoughts around simplifying some of the nav labels (like Activity Schedule Summary = Activity Schedule). Why is this label "State Cost Categories" instead of "State Costs"? Categories is a reference to a column in a table on the template, not the title of a section.
Also, I was looking back at the template and the only place that "in-house" is used, is on that Quarterly table, so it doesn't seem like it's an important enough term to be added to the nav, if it's not used on the State Cost page except in help text. To me it seems like the better move here would be to make the table consistent with the navigation and State Costs page.
cc @jeromeleecms thoughts?
State costs: I would want to explore "State Personnel and Expenses" (or some derivative of it). We wanted to rename the nav content so people knew what to expect in that section. I'm OK with avoiding the word "in-house" since we include the context in much of the help text and it only appears in the final table to align with what is in MBES.
Activity Schedule Summary: Not too opinionated on this, if have better words to describe this. I'm OK with it as is or "Activities Schedule" is also OK.
Open to simplification -- but let's also start thinking through how much content polishing we want to do. If it's clearly wrong, let's fix that -- if we start wandering down the path of perfection, we'll never finish :)
@jeromeleecms @CSwartzHMA what if we do it like this.
If we are aiming for consistency, should we label this as "State staff and other expenses" or "State staff and other state expenses" ? Though it's a longer label, this would be most consistent with how we refer to it within the application. But the spirit of the approach is fine.
I don't think it's important to be exactly consistent, but to get the gist across using the same terms. I don't think "other" is descriptive or proprietary enough to make a difference in the navigation.
I was looking for feedback on the the table label more than anything? Does this accomplish what we need to both show the user where to get back to the in the app and to let them know this is where this in-house cost lives?
My only thought is that it might help to switch the label in the table to In House Cost (State staff and expenses) keeping the table consistent with the MDBTs, but I could go either way with that. Otherwise, I think this will work and we can see if it seems smoother in the next round of user research.
Sounds good - I'm fine with how Jenn proposed this and per Caryn's suggestion we can just put this in front of people in our next round of research.
State needs: medicaid detail budget table, and quarterly reports to show they did their funding appropriately, a related federal form rolls up costs into all state costs = in-house costs. The in-house costs line in the table shows this roll up of state staff and other state expenses.
Federal use: will use info to import (copy/paste) to mastertables.
Per convo with Caryn, let's go with what's in the mock up for now and keep an eye on this as a potential issue.
@thetif this is ready for dev
Change log -
Make sure the export view reflects the recent changes to the headers:
Change "In-House Cost Categories: State Personnel" to Correct "State staff"
Change "In-House Cost Categories: Non-Personnel" to Correct "Other state expenses"
Nav bar and title for State Cost Category page do not currently guide users from other pages back to where data was entered if changes are needed later in the data entry process.
This task is done when...