You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The screenshot below, from a Teams chat, is not a good way to manage "small batch" design requests. What is the absolute minimum viable version of something to wrangle this work?
Some issues with this:
Requester has defined the role and the specific work to be done
Request is framed in terms of LOE as opposed to the available budget
Request includes ask for a specific person
In general, these are things that should be determined by the Design team.
Instead, the request should focus on things like:
What is the desired outcome? (In this case, something like, "we want to learners to be able quickly scan and identify content related to manufactured homes.)
What is the context for this work? (Need to see existing content/layout, style guide, other related items, etc.)
Do we have everything we need to get started? (Content checklist)
What is the desired delivery date? (With expectation setting for how we work backwards from that in various situations.)
How much time is budgeted for this work?
Are there any constraints on who can do this work?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The screenshot below, from a Teams chat, is not a good way to manage "small batch" design requests. What is the absolute minimum viable version of something to wrangle this work?
Some issues with this:
In general, these are things that should be determined by the Design team.
Instead, the request should focus on things like:
Beta Was this translation helpful? Give feedback.
All reactions