Architect Flow- RM Facing

Jobs

RM: oversees the job from beginning to end

Architect: completes as much research as possible with agents.

Verifier: This person verifies sources. They can also pull data from a website you give them and place it in a spreadsheet or perform other less time-consuming tasks (i.e., locating social media profiles and recording that information).

Analyst: finishes the remaining research.

Exceptions to This Flow

Any exception will go through our old flow. We will create a proposal/outline and proceed as we normally would. We will not involve the architects at this point (once we figure out how to optimize this process, we will remove the exceptions).

  1. Urgent turnaround is needed.
  2. Weekends (we do not have weekend coverage at this point)
    1. Tight ETA- no architect, scope, and get to the dash or send for approval as needed
    2. ETA is flexible: set up the project for the architect and then post in #channel-yet-to-be-named. The architect will begin working on it Monday morning.
      1. If there is nothing to do on a weekend shift, the RM will set up rOS runs and place them in a document with headers correlating with the objectives.

https://lucid.app/lucidchart/99ecf973-b3a0-495d-8118-c2cacc23b931/edit?viewport_loc=3320%2C82%2C1664%2C773%2C0_0&invitationId=inv_2a4c7713-2543-42a4-b0bd-9e397ad67262

The easiest way to think about this is that you are the conductor. You have the ability to think about the research and decide how best to use the team. Maybe the architect can do the whole job. Maybe you locate a database and realize the verifier could easily take that information and place it in a table to save everyone time. Maybe you look at the research after the architect and realize you could make some tweaks, which would be client-ready. Other times, we will see that we need an analyst to ensure a comprehensive brief. The options are endless!

Test Project- RFP- Ritz-Carlton Yacht Collection

Proposal