What I was trying to do:
Create a post
What I expected to happen:
Obtain the same user experience as was designed for this feature in Figma
What actually happened:
I see two different screens (no chat in figma for resident) and post type not well written on two lines.
Order of type not the same as figma also.
See what I see on my app vs figma.
Screenshot from App |
Figma |
Critical Message to Product Team
We can't even send this bug to the dev team as
The requirements are completely unclear
There are many features packed up into one
The original feature was destroyed by new designs which have nothing to do with it
My comments / Concerns / Feedback @Paul-André Savoie
What happened to the original feature where the items were shown at the bottom, expanding from the X action button ?
This is an entirely new feature, deprecating the old one, why are we using an in production feature number to completely redo a new feature ?
Why did we redo this page ? We have hundreds of bugs, we're months late for launch, and now we've sent a completely redone a feature which had absolutely nothing wrong with it, only to insert new bugs, with unclear requirements, without having created any acceptance criteria, use case, user story (of this feature vs. original), nor any clickable prototype for devs or QA to validate exactly how to implement
What was the value (as measured by Aha! score of this new Create a Post type selector, vs. Old ? Did it warrant the new work for product team, dev team, qa team, and now, the bug fixing that is coming with it ?
I see the 'Chat with us' there too, which is another separate feature than the create a post selector itself. It is to be shown Only to EO's, not Residents, and this feature too, is not documented in any way, or sent to dev.
Once again, the feature sizes are way too large, and now, we're using features which are in production, and changing their figma's entirely, making testing impossible.