← Back to all projects Practice Project

Loopline Technologies — PM Portfolio

A full project-management build for a fictional app-launch client, from workspace setup through formal status reporting.

AsanaRisk ManagementStatus ReportingStakeholder Comms
Asana dashboard for Loopline Technologies App Launch, showing task completion by section

Overview

Loopline Technologies is a fictional client I built out to practice project management the way it actually happens on the job — not just theory. The brief: manage an app launch from planning through go-live, for an international team, with the kind of documentation a real client would expect to see.

Approach

  1. 01

    Set up the Asana workspace with Planning, Development, and Launch sections, each with clearly scoped tasks and owners.

  2. 02

    Built out a fictional six-person team spanning PM, development, QA, marketing, operations, and design, and assigned realistic tasks to each role.

  3. 03

    Compiled a 10-item risk register, identifying potential project risks with likelihood, impact, and mitigation plans for each.

  4. 04

    Wrote a formal project status report summarizing progress, blockers, and next steps in client-ready language.

  5. 05

    Pulled it all together into a styled, professional portfolio document with embedded Asana screenshots.

In Practice

Turning a Stand-up Into Status & Action Items

Not every status update starts from a clean template — sometimes it starts as sixteen minutes of cross-talk in a quick check-in. Part of the job is sitting in on that and pulling out what actually matters: what changed, what's blocked, and who owns what next.

Beta Feedback Check-in · 10:00–10:16am · On: Jordan, Aisha, Priya, Marcus, Grace · Not on: Daniel (design, out this week)

Priya kicked things off: the beta is out to 40 users with 28 responses back in week one — a solid return. The same complaint keeps surfacing — the onboarding flow is confusing, and specifically, 3 users dropped off right at step 2. That's the fix to make, not a full redesign.

Marcus wants to hold the webinar a few days rather than lock in messaging before more feedback comes in — no pushback from the team. Aisha can have the step-2 fix done by Friday, but only if it jumps ahead of her security review; Jordan approved on the spot, pushing the security review to next week. Grace is still waiting on final CS docs copy from Marcus — no change there. Priya is out next Tuesday, so that check-in needs to be pushed or covered async.

OwnerAction ItemStatus
AishaOnboarding step-2 fixDue Friday — now ahead of security review
MarcusSend final CS docs copy to GraceStill outstanding
MarcusConfirm new webinar date once more feedback is inOn hold, pending data
EveryoneNext check-inMonday — Priya's slot needs covering or pushing

Outcome

This project let me practice the full arc of project coordination — structuring work, tracking risk, and communicating status the way a real client or executive would expect. It's the exact skill set behind both EVA and project-support roles.

Interested in working together?

Let's talk about how I can help your team run smoother.

Get in Touch