Upskill & Growth Training

Master your craft, own your cases, deliver excellence

💡

Foundation: Our Culture

Excellence Over Completion
▼
  • We don't just finish tasks—we deliver solutions that exceed expectations
  • Every case is an opportunity to showcase what's possible
  • Our reputation is built on the quality of our worst work, not our best
Ownership Mindset
▼
  • If it's assigned to you, you're the CEO of that case
  • You own the outcome, the client relationship, and the solution quality
  • "I don't know" becomes "I don't know yet, but I'll find out"
Creative Problem-Solving
▼
  • The first solution is rarely the best solution
  • We explore, experiment, and innovate within boundaries
  • We challenge limitations respectfully and find workarounds intelligently
Client-Centric Thinking
▼
  • Understand the business goal behind every request
  • Midmarket and celebrity clients expect proactive communication and flawless execution
  • We represent the company's commitment to excellence in every interaction
1

Common Scenarios & Proven Solutions

Custom Functionality Requests

  • Scenario: Client wants custom request
  • Solutions: Always explore all options, including javascript implementation

Design & UI Modifications

  • Scenario: Custom new page/redesign
  • Approach: Follow client's branding/look for inspiration and good design practices
  • Mobile considerations: Always test responsiveness

Integration Challenges

  • Third-party APIs when our platform doesn't have what the client wants (like a calendar, etc)

VIP/Celebrity Client Scenarios

  • Extra testing requirements
  • Reach out to DPC for confirmation/extra help

Edge Cases & Workarounds

  • Platform limitations we've solved creatively: examples
  • "Impossible" requests we made possible
  • When to say no and how to say it: examples

How to Contribute

After solving a unique case, document it here. Include: problem, what you tried, what worked, why it worked (optional). Monthly review sessions to refine, update, share with the team.

Submit Your Case Study
2

AI Guide: How to Use AI to Be Faster Implementing Code

Logic Thinking Before Prompting
▼

Answer these BEFORE asking AI anything:

  • What is the client actually trying to achieve? (not what they asked for)
  • What data/elements do I have to work with?
  • What's the expected behavior in different scenarios?
  • What are the technical constraints? (platform, browser support, performance)
  • How will I test this?
Crafting Effective Prompts
▼

❌ Bad Prompt Example:

"Make a slider"

✅ Good Prompt Example:

"I need JavaScript for an image carousel on a Squarespace site that: - Auto-advances every 5 seconds - Pauses on hover - Has previous/next buttons - Works on mobile (touch swipe) - Doesn't use jQuery - Loads images lazily for performance The HTML structure is: [paste structure] Please explain the key functions so I understand how to modify it later."

The Prompt Template:

Context: I'm working with [platform/framework] Goal: I need to [specific outcome] Requirements: - [Requirement 1] - [Requirement 2] - [Constraint 1] - [Constraint 2] Current situation: [What you have/tried] Please: [Explain/provide alternatives/focus on X]
For Debugging
▼
  1. Describe what should happen vs. what is happening
  2. Share relevant code snippets only
  3. Mention what you've already tried
  4. Ask AI to explain WHY something isn't working
For Learning
▼
  • "Explain this code like I'm intermediate with JavaScript"
  • "What are alternative approaches to this problem?"
  • "What are the performance implications of this solution?"
  • "What could go wrong with this implementation?"
AI Tool Selection
▼

ChatGPT/Claude:

  • Problem-solving and logic
  • Code explanation and learning
  • Multiple solution approaches
  • Architecture decisions

GitHub Copilot/Cursor:

  • Real-time code completion
  • Boilerplate generation
  • Pattern repetition
3

Decision Matrix: When to Push vs. Escalate vs. Redirect

🟢 PUSH FORWARD You Own This

Criteria:

  • Within platform's documented capabilities (or has proven workaround)
  • You have the technical skills/can learn quickly with AI assistance
  • Timeline is reasonable for exploration and testing
  • Solution won't impact other clients or systems
  • Falls within your authority level

Examples:

  • Custom CSS/JavaScript for UI modifications
  • Form validation and user interactions
  • Integrations with documented APIs
  • Creative implementations using existing features

Your Action: Explore multiple solutions → Test thoroughly → Document your approach → Deliver with confidence

🟡 ESCALATE INTERNALLY Loop in Leadership First (DPC)

Criteria:

  • Requires access/permissions above your level
  • Budget implications uncertain
  • Timeline is tight and risk is high
  • Security or compliance implications
  • Could affect site stability or performance significantly

Examples:

  • Custom features that might become ongoing maintenance
  • Changes to core platform functionality
  • Solutions requiring significant client budget

Your Action: Document what you've explored → Prepare your recommendation → Present to team lead → Don't promise client anything yet → Stay involved in the solution

"I want to make sure we handle this optimally. I've explored [approaches], and before committing to the client, I'd like your input on [specific decision]. My recommendation is [X] because [reasoning], but I want to confirm this aligns with [company policy/client tier expectations/budget]."

🔴 REDIRECT TO ANOTHER TEAM Outside Our Scope

Criteria:

  • Requires backend/database architecture changes
  • Platform limitation with no viable workaround
  • Needs expertise outside your domain (design overhaul, infrastructure, etc.)
  • Third-party integration not yet supported by platform
  • Better suited for different team's tools/expertise

Examples:

  • Custom database structure
  • Server-side processing requirements
  • Complete design rebrand (vs. design tweaks)
  • Email server configuration
  • Advanced SEO/analytics setup requiring backend access

Your Action: Thoroughly document why this needs redirect → Identify the right team/person → Warm handoff: brief them with context → Stay as liaison if needed