top of page
Request for Product Flow
We were a tiny team and needed help with our art creation, especially for the scrolling backgrounds. I took on the task of writing the requests as well as working with out outsourcers
Programs used:
Google docs, Adobe Photoshop/Illustrator/AE, Jira
problem:
-
The team was small, only 2 designers, 2 artists, and 3 developers. With such a small team it was becoming impossible to both add new features while also releasing new level content every 2 weeks.
pain points:
-
Since this app was a variant of 2 other applications merged together a lot of our processes were complex and confusing
-
There was also no existing documented process or style guides regarding the level release content.
finding a provider:
To find an external team to help us produce content I decided to test 2 different teams to figure out which team was more detail oriented, able to take direction, and willing to ask questions when they were confused
documentation:
-
I had to create a detailed documentation that could be understood clearly and easily. Using a mixture of visuals and detailed instruction I hoped to convey clearly to the two teams being tested.
-
Along with the documentation I decided to make a library of blank templates with the documented aspect ratios and guides. I hoped with these guides all delieverables would be the correct size listed in the documentation
example of created documentation
external test insights:
-
On inspection of the tests the team came to an agreement on one over the other. The chosen team taken better instruction and delivered all assets as asked for.
-
After the test I became aware of some areas that my documentation needed more details and instruction, which I remedied as we moved forward to the next request for product.
refining workflow:
-
I knew there was always going to be room to improve, so whenever a miscommunication or delay in delivery happened I made note and aimed to resolve the issue in the documentation.
-
I developed a checkin schedule for the external team, where they would send their current progress. I would then note any feedback and send it back. This helped ensure both parties were aligned.
examples of feedback
results:
After a 3 week design process, and a total of 6 checkins (including the final delivery) We came to this final design.
conclusion:
While documentation kept growing and changing to improve on it, sending this content to an external provider allowed the team to focus on features as desired. It served a dual purpose as well when on-boarding new team members.
bottom of page