Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix numbering on Low-income Basic Flow #1912

Closed
thekaveman opened this issue Feb 27, 2024 · 4 comments
Closed

Fix numbering on Low-income Basic Flow #1912

thekaveman opened this issue Feb 27, 2024 · 4 comments
Assignees
Labels
documentation [auto] Improvements or additions to documentation product Issue captures work for the product team

Comments

@thekaveman
Copy link
Member

The chart shows 11 steps:

image

But the list only has 9 steps:

image

Expected behavior

The chart is (correctly) showing all steps in the process, while the list presents a more plain-language (and still correct) version of the process. Suggest removing the numbering from the chart (other flow charts do not have numbering) to avoid confusion.

@thekaveman thekaveman added bug Something isn't working documentation [auto] Improvements or additions to documentation labels Feb 27, 2024
@indexing
Copy link
Member

@thekaveman I can see how you read the diagram and the basic flow together, but my intent was for each to have a distinct purpose.

  • The diagram shows each technical step in benefit enrollment and the sequence of system actions, as well as the relationship, between services and platforms.
  • The basic flow, on the other hand, lists the steps a user (transit rider) takes to complete enrollment. It describes both what the user does and how the system responds to those inputs.

Including the step to choose a transit agency, for example, is too granular for the diagram as that's a UI interaction. Step 5 in the flow is brief and covers several backend calls and responses in the diagram.

Thus, I see them as complementary and don't believe they have to align verbatim.

If we want to make it more clear that they are distinct, I propose adding a header to the diagram that reads something like Technical Architecture and moving the the Basic Flow header above the sequence.

@thekaveman
Copy link
Member Author

@indexing I follow you. I think I was tripped up mostly on the numbering on the flow chart, especially since the other flow charts do not have numbering. Should we be consistent here (one way or the other)?

@indexing
Copy link
Member

indexing commented Mar 4, 2024

@thekaveman For me, the numbering in the chart is a helpful affordance to understand the process as a sequence and the numbering makes it a bit easier to step through the phases when scanning. I do note the numbering is new in this diagram; I propose adding it to the others (which I will do). Any objections? Maybe add this as a task in #1812 ?

@indexing indexing moved this from Todo to In Progress in Digital Services Mar 4, 2024
@thekaveman
Copy link
Member Author

Closing as this is being tracked in #1812.

@thekaveman thekaveman closed this as not planned Won't fix, can't repro, duplicate, stale Mar 6, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in Digital Services Mar 6, 2024
@indexing indexing added product Issue captures work for the product team and removed bug Something isn't working labels Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation [auto] Improvements or additions to documentation product Issue captures work for the product team
Projects
Archived in project
Development

No branches or pull requests

2 participants