2.1 Artifact Index

Artifact 1 - SMART Goal: Balancing Full-Time Work Development

Artifact 2 - Personalised Mentorship Plan (OECS Module 2)

Artifact 3 - Resume Writing (Professional Branding)

Artifact 4 - Workplace Conflict Recognition & Resolution

Artifact 5 - Stressors & Work–Life Balance (SMART Plan)

Artifact 6 - Budgeting Basics & Financial Goal Setting

2.2 Artifact Entry

Artifact 1

Productivity & Professional Practice module, tied to ongoing Dweevay/Pelican Tours work;

A structured SMART plan to sustainably dedicate 10 hours weekly to web/app development alongside a full-time job. It includes a time-blocked schedule, explicit deliverables (one shipped feature, one case study, and one bug fix/API improvement), measurable metrics (≥80 hours, ≥4 commit days/week), and a weekly review cadence.

Skills demonstrated:

Time management, goal design, evidence tracking, delivery focus, and reflective practice.

Tools/Stack:
Google Calendar, Google Sheet time tracker, Pomodoro timer, Git/GitHub, project backlogs (Dweevay/Pelican Tours).

Reflection - Balancing full-time work with meaningful development required me to shift from ‘finding time’ to ‘allocating time.’ The SMART framing forced clarity: a fixed 8‑week window, weekly 10‑hour target, and three tangible outputs. The biggest change was starting each session by ranking tasks with an Eisenhower lens; this prevented me from sinking hours into low‑leverage busywork and kept attention on deliverables that moved users forward. Working in Pomodoros highlighted my natural cadence: deep focus peaks on Sunday afternoons, and lighter, diagnostic work fits best midweek. Logging hours and commits surfaced two patterns: (1) small, daily progress beats weekend sprints for code quality and (2) writing a brief intent statement before coding reduces context switching and rework. I also learned to right‑size scope. When fatigue set in, I broke features into thinner slices and shipped a vertical sliver end‑to‑end; this kept momentum and provided earlier feedback. Trade‑offs were necessary: I postponed nonessential polish, documented what was deferred, and set a time to revisit it.

The most valuable outcome wasn’t just the ≥80 hours; it was the habit loop: plan → execute → review → adjust. That loop improved estimation, made my work more predictable to collaborators, and increased confidence. Going forward, I will keep the Sunday 3‑hour deep‑work anchor, maintain ≥4 commit days/week, and continue weekly reviews linked to user‑visible outcomes. I will also formalize a simple rubric for deciding when to refactor versus extend, so quality keeps pace with delivery. Overall, this artifact demonstrates disciplined self‑management that directly translates to reliable, user‑centered delivery in live projects.

Learning Outcomes Alignment:

• Demonstrates independent learning via structured practice and self‑assessment.
• Applies professional tools and workflows to deliver working software reliably.
• Communicates progress transparently through metrics, documentation, and reviews.
• Reflects critically on process, trade‑offs, and next steps for continuous improvement

Artifact 2

This personalised mentorship plan outlines how I will leverage mentorship to strengthen software development and digital business skills while contributing to community‑focused IT projects. It ties my strengths (problem‑solving, teamwork, and self‑directed learning) to clear goals and addresses growth areas in assertiveness and time management through structured practice and accountability.

Advanced Digital Skills scholarship; Module 2 - Empowering for Success in the Workplace.

A complete mentorship plan including a SWOT summary, career strengths mapping, two SMART goals, focus areas, preferred mentorship style, and a progress‑tracking strategy (weekly reflections, Trello/Notion board, monthly mentor check‑ins). The artifact demonstrates intentional design of a growth framework anchored in real deliverables and feedback loops.

Skills demonstrated:
self‑assessment, goal design, stakeholder alignment, professional communication, progress measurement, and reflective practice.

Tools/Stack:
Google Docs, calendar scheduling, feedback log, and community networking.

Reflection - Designing a mentorship plan pushed me to connect who I am with how I will grow. The SWOT made hidden patterns visible: I rely on self‑direction and problem‑solving, yet I sometimes hesitate to ask for help precisely where mentorship adds value. Translating that insight into two SMART goals created a bridge from intention to action: one goal to ship a functional community‑focused digital project and a second to improve communication through deliberate exposure (events, feedback, and practice). The most beneficial aspect was establishing a regular schedule of weekly reflections and monthly mentor check-ins - because growth requires rhythm, not random effort. I also learned the importance of framing: stating the 'why' for each goal clarified its relevance and allowed me to prioritize when time was short. In practice, I expect friction from fatigue and competing commitments; to counter that, I will front‑load higher‑cognitive tasks, protect a weekly deep‑work block, and prepare ‘help‑seeking prompts’ so I can ask focused questions instead of delaying. The preferred mentorship style section reminded me that I learn best through hands‑on work, candid feedback, and examples that reveal decision criteria, not just answers. That insight will shape my sessions: bring a small artifact, discuss trade‑offs, and leave with one actionable experiment. Overall, this artifact demonstrates that professional development can be engineered: define outcomes, install feedback loops, and measure progress. The plan is simple enough to follow, yet structured enough to reveal whether it’s working. Next, I will convert Goal 1 into a tracked backlog with milestones, schedule three networking interactions tied to Goal 2, and use mentor feedback to sharpen my communication under time pressure.

Learning Outcomes Alignment:

• Designs a professional growth plan aligned to career objectives and community impact.
• Applies SMART methodology to create measurable, time‑bound goals.
• Demonstrates reflective practice and feedback integration to improve performance.
• Communicates clearly with stakeholders and structures check‑ins for accountability.

Artifact 3

This artifact captures the redesign of my professional resume to position me as a web & mobile app developer focused on React Native (Android/iOS) and WordPress/WooCommerce for e‑commerce. The work aligns with my active projects (Dweevay, Pelican Tours, and Powertranz 3DS2) and the OECS program’s emphasis on employability and career readiness.

I restructured my resume around outcomes and projects, leading with ‘Web & Mobile App Developer’ and highlighting React Native, WordPress/WooCommerce, Mapbox, and 3DS2 security flows. The document now foregrounds measurable, job‑relevant accomplishments, uses ATS‑friendly keywords, and presents ‘Selected Projects’ before legacy roles.

Skills Demonstrated

Professional communication, ATS optimization, outcomes‑based bullet writing, project storytelling, and skills mapping to role requirements.

Tools/Stack

Microsoft Word/Google Docs, LinkedIn profile tuning, ATS keyword research, GitHub.

Reflection - Rewriting my resume clarified both positioning and proof. Leading with ‘Web & Mobile App Developer’ aligned the headline with the work I actually do—React Native features, WooCommerce integrations, and secure 3DS2 checkouts. Moving ‘Selected Projects’ upfront changed the conversation from job titles to tangible outcomes users and stakeholders care about: reliable builds, faster issue resolution, and successful transactions. Focusing bullets on action + context + result exposed where I had listed tasks instead of impact; tightening language forced me to quantify value (uptime, speed of fixes, security compliance) and link it to business outcomes.

Optimizing for ATS taught me to mirror market language without buzzword stuffing. Keywords like React Native, TypeScript, Android (Gradle), iOS (Xcode), WordPress, WooCommerce, Mapbox, and 3DS2 map cleanly to my portfolio and code history, which strengthens credibility. The biggest learning was narrative flow: a recruiter should understand who I am, what I’ve shipped, and why it matters in 10 seconds. That drove layout choices, concise bullets, and clearer section headings.

Practically, the process surfaced gaps I can close next: short demo videos for Dweevay features, a one‑page 3DS2 case study, and consistent commit history screenshots for evidence. I’ll measure impact by tracking LinkedIn profile views, response rates to applications, and interview requests in the next 60–90 days. Overall, the artifact demonstrates professional communication and self‑assessment: the resume now tells a coherent story that connects skills, projects, and results to roles in the Caribbean digital economy.

Learning Outcomes Alignment

• Communicates professional value clearly and concisely to employers and collaborators.
• Aligns skills and projects to market needs using evidence and outcomes.
• Applies iterative improvement using feedback (ATS checks, AI prompts, mentor input).
• Demonstrates readiness for web/mobile roles through relevant, verifiable artifacts.

Artifact 4

Conflicts in the workplace often stem from differing priorities, unclear expectations, or miscommunication. This artifact synthesizes key sources of conflict and practical strategies for resolution, anchored by Kevin Giraldo’s video on common sources of workplace conflict and a real‑world scenario involving late work submissions.

The artifact summarizes common conflict sources, outlines an eight‑step resolution approach, and applies these to a concrete case: an employee consistently submitting work late. It demonstrates how to combine empathy, data, and workflow adjustments to restore trust, improve delivery, and maintain professionalism.

Skills Demonstrated

Active listening, de‑escalation, mediation, expectation setting, workflow design, delegation, and accountability with empathy.

Tools/Stack

SBI feedback (Situation–Behavior–Impact), RACI roles, Kanban or task board with WIP limits, calendar SLAs, 1:1 agenda template, and risk‑early‑warning checklist.

Reflection - This exercise reframed conflict from a personal failing to a solvable system problem. Starting with listening before prescribing revealed that late submissions often combine unclear expectations with uneven workloads and hidden blockers. Using the SBI framework kept the conversation respectful and specific, while a visible task board and WIP limits turned vague complaints into actionable flow data. The key learning was balancing empathy with accountability: acknowledging real constraints and then co‑creating a plan with measurable steps (SMART targets, early‑risk signals, weekly check‑ins). That combination reduced defensiveness and increased ownership.

I also saw how small process tweaks compound: clearer acceptance criteria prevented rework, a 24‑hour risk signal enabled timely help, and RACI charts cut confusion about who decides vs. who executes. Importantly, the conversation expanded from one person’s lateness to a team‑level improvement in how we size work, negotiate deadlines, and communicate when priorities change. I will measure impact through on‑time completion rate, cycle time, and the number of spillovers between weeks. If metrics improve yet tension remains, I’ll revisit psychological safety cues (how we ask for help, how we respond to slips) to protect trust.

Overall, I learned to intervene earlier, frame issues with data and impact, and fix both behavior and the system around it. This approach translates directly to software delivery: better flow, fewer surprises, and healthier collaboration.

Learning Outcomes Alignment

• Identifies sources of workplace conflict and applies structured resolution strategies.
• Demonstrates professional communication through active listening and SBI feedback.
• Improves team delivery by aligning expectations, redistributing workload, and setting SLAs.
• Uses reflection and metrics to drive continuous improvement in a real scenario.

Artifact 5


Recognizing workplace stressors and tight deadlines, workload pressure, and workplace conflicts is the first step toward effective self‑management. This artifact converts my stress self‑assessment into a concrete SMART plan focused on balancing family life and work life through boundaries, time‑blocking, communication habits, and mindfulness.

Turning a broad intention, ‘balance family and work,’ into a specific, measurable routine forced me to decide what balance actually looks like day‑to‑day. Two patterns stood out from past weeks: chores were either crammed into late nights or postponed until they piled up, and work communication tended to happen reactively, only after something slipped. The new plan addresses both by time‑blocking chores and scheduling short, proactive updates to teammates or my supervisor. That shift from reacting to planning reduces last‑minute stress and keeps expectations aligned.

The other key insight is that small mindfulness breaks have outsized benefits when used at the right moment between deep‑work blocks or before evening chores when energy dips. A five‑minute breathing practice or a short walk resets attention and reduces the friction of starting. By tracking mood weekly alongside hours and check‑ins, I’ll be able to see whether the routine is helping, not just whether I did the tasks. If the data shows a mismatch between hours completed but mood flat, I’ll adjust the distribution (e.g., shift a chore block to Saturday morning or shorten a weekday session).

This plan is deliberately simple so it survives busy weeks: one calendar, one notes page, and short, respectful communication. If a day derails, the Sunday review helps me reset the plan without guilt and carry forward what works. Success here isn’t perfection; it’s a sustainable rhythm that keeps home responsibilities and professional commitments visible, planned, and supported by mindful pauses.

Learning Outcomes Alignment

• Identifies personal workplace stressors and designs a SMART intervention.
• Implements time‑blocking and communication habits to improve balance and reduce stress.
• Uses mindfulness and digital tools to support well‑being and productivity.
• Tracks evidence (hours, check‑ins, mood) and reflects for continuous improvement.

Artifact 6

This artifact applies the 50/30/20 budgeting rule to a starter salary scenario (EC$2,200) while contributing to family household costs, servicing a student loan, and building an emergency fund. The plan uses clear category caps, line‑item detail, and measurable savings/debt goals.

Reflection - Applying the 50/30/20 rule to EC$2,200 made trade‑offs explicit and helped me create a realistic plan that still moves me forward. Keeping ‘Needs’ at 50% required line‑by‑line choices; sharing utilities and a disciplined transport/mobile budget kept essentials predictable. Placing ‘Selected Wants’ at 30% stops impulse creep and gives me permission to enjoy small experiences while staying responsible. Most importantly, locking 20% for ‘Savings & Debt’ creates momentum: EC$250/month builds an emergency fund in about a year, and the extra EC$90 against the student loan starts a debt‑snowball habit.

The exercise also highlighted risk points. If a surprise cost hits, the first step is trimming ‘Wants’ by 10–20% and diverting that to emergencies. If income changes, I will adjust the percentages temporarily but keep the emergency fund contributions alive, even if smaller, to protect progress. Tracking this plan in a simple spreadsheet will make patterns visible—especially months where gifts/social expenses spike or when transport costs rise. If I consistently beat the plan, I’ll shift part of ‘Wants’ into faster debt payoff to shorten the time horizon. Overall, this budget balances today’s quality of life with long‑term stability and gives me a concrete playbook for the unexpected.