Greg Roque Natividad

Sport Club 4Tactic ran its whole operation through Facebook posts, group chats and printed notices. No one owned announcements, so members got schedule changes late or not at all, and coaches re-typed the same fixture list into three places. Two tournaments had turnout problems traced back to an update that never reached half the squad. Previous attempts to "just use one group chat" failed because nobody could say which chat was official. Agreed a single official source with the committee, with a named owner per section rather than a shared account. Announcements moved to a weekly routine: drafted in Confluence, approved by the section owner, published to one channel, with fixtures mirrored to the club calendar. Ran old and new channels side by side for one month so nothing was missed, with a rule that anything posted only to the old channel was re-published, not lost. Urgent changes inside 24 hours escalated straight to the section owner and the committee chair. After the parallel month, old channels were closed to posting and kept read-only. No tournament since has lost turnout to a missed update. Coaches stopped re-typing fixtures into three places, and the committee can point to one channel when a member says they were not told.

The club committee requested, for Q4, an update to the 4Tactic app: refreshed buttons and front-end design, plus a new dashboard that analyses customer data and shows each member what they need to see. The request arrived as a single wish list with no scope, no owner and no order of work, and the last release had slipped because tasks were handed out ad hoc and nobody knew what "done" meant for each piece. The request went first to the section owner, who checked the team had the capacity and skills for the quarter and confirmed it could be taken on. As project manager I turned the wish list into a scope note and a RAID log, then planned the work in Jira with milestones for design freeze, build, QA and release. I distributed the tasks by discipline: the UI/UX designer was assigned the button and screen redesign in Figma with the approved style guide as the acceptance criterion; the front-end developer was assigned implementing the new buttons and layouts from the Figma spec, accepted when every screen matched the design and passed responsive checks; the back-end developer was assigned the data-analysis service and dashboard API, accepted when the endpoints returned the agreed customer metrics within the performance budget; QA was assigned the test plan and regression run, accepted when all acceptance criteria passed with no open critical defects. Progress was tracked in weekly stand-ups and a Confluence status page, blockers escalated to the section owner within a day. Each completed piece was submitted for approval to the committee; anything not approved was sent back with the reviewer's notes for improvement and re-submitted, and only an approved build was published. The Q4 update was published on schedule with the redesigned front end and the new customer dashboard live. Every task had a named owner and a written acceptance criterion, two pieces went round the approval loop once and came back right, and the committee signed off the release without a post-launch hotfix.

Distriphil needed a structured digital platform to present its pharmaceutical products and services to customers and partners. The PM scoped requirements with stakeholders, broke the site into owned deliverables, and distributed work across design, development, content, and QA with clear acceptance criteria and consolidated feedback loops. The result was a launched website and a repeatable, ownership-driven workflow that reduced unnecessary back-and-forth across the team.

MUMS required an e-commerce website to sell Swedish candy products, covering product pages, collections, promotions, gift options, and checkout. The PM scoped the site into six parallel workstreams, assigned each to a specialist, and managed dependencies and review gates across UI/UX, front-end, e-commerce, content, and QA before stakeholder sign-off. A mid-project rework loop caught checkout and responsive layout gaps before go-live, resulting in a structured shopping experience and a repeatable workflow for future campaigns.

Four siloed teams—marketing, production, ticketing, and operations—were racing toward the same event deadline with no shared tracker, no clear ownership, and overlapping dependencies that no one could see. The PM centralized everything into Jira, defined workstreams, assigned owners, and ran weekly escalation reviews to surface blockers before they became crises. The result was a single source of truth that gave leadership real visibility into readiness and eliminated the last-minute scramble that had defined previous events.

A hotel operation was running on fragmented communication channels, leaving tasks without clear owners or deadlines across front office, housekeeping, maintenance, and management. A centralized Jira-based tracker was scoped, planned, and distributed across departments—with owners, priorities, deadlines, and dependency mapping enforced from intake through resolution. The result: management gained live visibility into outstanding work, teams had a structured follow-up process, and potential delays were caught earlier.

An energy asset integration was at risk of slipping because requirements, dependencies, and testing status were scattered across conversations and tools with no single owner view. The PM centralised the delivery into a structured plan in Jira and Confluence, assigned defined workstreams to engineering, QA, and operations with explicit acceptance criteria, and introduced a regular review cadence to surface blockers before they reached the rollout. The result was earlier blocker identification, clearer stakeholder visibility, and a controlled release with documented scope changes throughout.

A fragmented, multi-channel issue-tracking system left the team unable to prioritize bugs or confirm release readiness before go-live. The PM centralized all requests and defects into a structured Jira workflow, scoped each item with stakeholders, distributed work to developers and QA with defined acceptance criteria and deadlines, and enforced a sign-off gate before release. The result: clearer ownership, earlier defect detection, and a lower risk of unresolved issues reaching production.

A multi-team product launch was losing coordination across international suppliers, marketing, design, and operations—with no single view of who owned what or which delays were cascading. The PM centralized the work into a structured launch plan with defined workstreams, owners, dependencies, and escalation paths across six specialist teams. The result: a single source of truth that surfaced blockers earlier, clarified accountability, and brought all teams to a coordinated go-live.

A multi-brand product launch was stalling because specifications, supplier timelines, creative assets, and marketing deliverables were scattered across disconnected channels with no shared owner list or dependency map. The PM centralized everything into a single plan divided into six workstreams, assigned explicit owners and deadlines, and ran structured escalation loops to surface blockers before they hit the launch date. The result was a single source of truth that gave every stakeholder real-time visibility into readiness and allowed the team to absorb scope changes without missing the go-live.

A growing e-commerce operation had product listings, creative assets, promotions, and marketplace updates scattered across teams with no shared visibility or ownership. A centralized tracker was scoped, workstreams defined, and tasks distributed with explicit owners, deadlines, and dependencies across product, content, and marketing. The result was a single source of truth that surfaced blockers early and replaced ad-hoc coordination with a repeatable, channel-spanning workflow.

An event organiser needed a single coordinating structure to bring registration, logistics, marketing, volunteers, and race-day operations to a fixed race date without collisions or last-minute failures. The PM scoped all workstreams, mapped dependencies across vendors and partners, distributed ownership through a centralised plan, and ran structured progress reviews with a risk-escalation loop. Mid-project blockers were surfaced early and re-routed before reaching critical milestones, replacing ad-hoc coordination with a traceable readiness checklist.

A cycling event organiser needed cross-functional coordination across registration, logistics, marketing, vendors, and race-day operations against an immovable race date. Work was broken into named workstreams with explicit owners, dependencies, and milestones; regular reviews and a readiness checklist surfaced blockers early. Accountability tightened as the event approached, replacing ad-hoc chasing with structured hand-offs and documented sign-off gates.

A multi-team apparel brand needed a repeatable, coordinated process for launching new collections across six functional areas—product, design, content, e-commerce, inventory, and marketing—where a single change could delay go-live for every downstream team. The PM scoped the full launch into parallel workstreams, assigned owners with explicit dependencies and deadlines, and built a central plan so blockers surfaced before they became launch risks. The result was a single source of truth that replaced scattered handoffs with a structured, reviewable release process.

A pet products business needed one coordinated system to manage product information, supplier sourcing, inventory, listings, creative assets, and promotions across six separate teams. The PM scoped the initiative, broke it into owned workstreams with explicit dependencies and deadlines, and ran a structured review gate before each launch. The result was earlier visibility into blockers, clearer ownership, and reliable coordination between product, inventory, e-commerce, and marketing.

A hospitality brand needed to coordinate multi-contributor events — venues, chefs, DJs, creatives, and brand partners — against fixed event dates with tightly interdependent deliverables. A centralized project plan was scoped, distributed across seven workstreams, and tracked through structured check-ins, escalation protocols, and a pre-event readiness gate. The result: a single source of truth that surfaced blockers earlier, clarified ownership, and made cross-functional coordination measurably more structured.

A window-covering business needed end-to-end coordination across consultants, manufacturing, inventory, and installation teams—each custom project carried unique measurements, approvals, and hard installation deadlines. A centralized tracker was scoped, planned, and distributed across all specialist owners with milestone deadlines and documented dependencies. When specification changes or delays surfaced, escalation paths and a pre-installation quality gate caught issues before they reached the customer.

A hospitality platform rollout demanded simultaneous coordination of requirements, data migration, integrations, testing, and training across multiple client environments with no shared tracking. The PM centralized the plan in a single implementation framework, defined milestone owners and acceptance criteria per workstream, and introduced a readiness-gate before go-live. When integration blockers and data delays surfaced mid-project, a prioritized issue log and dependency mapping kept the schedule from slipping silently.

An electronics retailer needed a single operational view across online listings, inventory, promotions, payments, and store pickup — seven functional areas that each moved on different timelines and ownership. The PM built a centralized tracker, mapped every dependency and approval gate, and distributed ownership across specialist teams with explicit deadlines and acceptance criteria. The result was earlier issue detection, cleaner cross-channel coordination, and a verified go-live checklist that kept product, pricing, and fulfillment updates in sync.

A fresh and frozen food operation needed structure across production, inventory, wholesale, e-commerce, and refrigerated delivery — all with product-specific timing dependencies. The PM centralized planning in a cross-functional tracker, mapped dependencies from preparation through delivery, and distributed ownership across five operational teams. When blockers surfaced — stock gaps, scheduling conflicts, order mismatches — an escalation and verification loop caught issues before they reached customers, replacing reactive firefighting with a repeatable coordination model.