Purpose of System
The purpose of having this system is to create a framework that processes communication requests to:
- Deliver high-quality content consistently,
- At the shortest time possible,
- And in order of the highest priority.
Current Process
Stage 0: In our current communication process, content would be requested on different channels within Slack, #growth, e.t.c.
Stage 1: When the content was requested, the requester would expect content writer to begin work on the content immediately, which she would do.
Stage 2: During which pass on requested details to the graphic designer, who would also begin working on the graphic asset for the content.
Stage 3: After both the copy and graphic are completed, they will be shared with Seun who reviews.
Stage 4: Afterward, it is shared on the #Communications_PR channel for the requester and the CEO to review and give feedback simultaneously.
Stage 5: Before the content is then released to our users.
Problems with the current process
- Content creation is not prioritized: Because there is no section in this process that ensures that the time of the comms team is spent on the highest priority tasks. Requests are completed on a first-come-first-serve basis, which is not optimal.
- Inspections and reviews are subjective: There is no written set of factors that define what high quality of content is during reviews and inspections. This process does not ensure that content writer and graphic designer improve over time because they do not know what underlying factors influenced a recommended change to be made by the reviewer, they end up making the requested change in the immediate but will repeat the same mistake in the future.
- Grammar is dynamic: Because the English language is dynamic, sentences can be written in different ways but still be grammatically correct. But the individual who is inspecting might not be familiar with the phrase, causing them to flag it as incorrect, which leads to an increased back and forth, slowing down the delivery time.
New Process
Stage 0: Comms requests are shared centrally on the #Communication_PR channel only.