create a flowchart with the below steps "3. Eight-Week Timeline • Week 1 - 2: Set the…
- User
create a flowchart with the below steps "3. Eight-Week Timeline • Week 1 - 2: Set the direction: Theme selection, objectives, budget, sponsors, Problem statement collection and finalization. • Formation of Hackathon Core Committee • Define Objectives • Theme Selection Workshop: Suggesting a 2-hour brainstorming session with the FutureWorks Lab panel. • Artificial Intelligence • GenAI • Developer Productivity • Customer Experience • Automation • Cyber Security • Sustainability • Cloud Optimization • Internal HR Automation • Product Innovation Top 3-5 Themes can be approved. • Problem Statement Collection: Collect real business problems from different departments. • Submission Template: Problem Title Current Challenges Expected Business Benefit Users Impacted Suggested Technology Expected Outcome
• CoE Review based on the below: Business impact Innovation opportunity Technical feasibility Product relevance • Week 3: Open the funnel: Launch announcement, invitations, registrations • Communication Campaign • Registration via MS Forms, Employees submit: Team Name Team Members Department Proposed Challenge Theme Brief Solution Tech Stack Team Lead Maximum Team Size 4-6 Members Cross-functional teams encouraged
• Registration period of 7 days, HRBP to ensure max participation. • Initial Screening by HR based on the below: Eligibility Team Size Duplicate Ideas • CoE Review: The CoE panel reviews all submitted nominations. Criteria Weight Originality 25% Business Need 25% Innovation 20% Technical Feasibility 15% Customer Value 15%
• Post review, the Registered teams list, Approved teams. Mentor Allocation will be shared.
• Week 4: Build strong teams: Team formation, mentor allocation, kickoff Kickoff Session to explain Rules Timelines Deliverables Judging Criteria Demo Expectations Mentor Introduction
Mentor Allocation Each team should prepare: Working Prototype Source Code Presentation Deck Business Case Architecture Diagram
• Week 5 - 6: Execute and deliver: Development sprint and checkpoints • Development Sprint: Teams work on their solutions. Weekly checkpoints o Architecture Review o Technical Review o Business Validation o Product Guidance • Prototype completion, testing, submission • Prototype Submission which includes: Working Model PPT (Maximum 10 Slides) Source Code Git Repository Architecture Diagram Demo Video (Optional) Business Impact Summary
• Compliance Review: HR + CoE verify Submission completeness Eligibility Functional prototype
• Week 7: Demo Day and judging Activity Time Solution Presentation 5 Minutes Live Working Demo 5 Minutes Judge Q&A 5 Minutes
• Suggested Presentation Structure
- Problem Statement
- Current Challenges
- Proposed Solution
- Technical Architecture
- Live Demonstration
- Business Value
- Future Roadmap Criteria Weight Innovation 30% Business Value 25% Technical Quality 20% Customer Impact 15% Presentation & Demo 10%
• Week 8: Awards, pilot planning, knowledge sharing
Awards can be categorised as: Hackathon Champion Runner-Up Best AI Innovation Best Customer Impact Best Technical Solution People's Choice Award Most Innovative Idea Emerging Innovator Award
- Planning Phase • Define hackathon theme. • Publish rules and evaluation criteria.
- Communication Plan • T-30: Save the Date email • T-21: Official launch with theme • T-14: Registration reminder • T-7: Team formation • T-3: Mentor introductions • T-1: Final logistics mail • Event day: Live updates • Post event: Winners announcement
- Registration • Online registration form • Individual or team registrations • Skill-based team balancing • Maximum 4–6 members/team • Manager approval (if required)
- Kickoff • Opening keynote • Problem statement briefing • Rules walkthrough • Judging criteria • Mentor introductions • Development begins
- Development Sprint • Daily mentor office hours • Technical checkpoints • Teams support channels • Mid-sprint review • Prototype freeze before Demo Day
- Demo Day • 5-minute product demo • 3-minute Q&A • Live prototype mandatory • Architecture overview • Business impact presentation
- Judging Criteria Criterion Weight Innovation 30% Business Value 25% Technical Quality 20% Customer Impact 15% Presentation 10%
- Winner Finalization • Individual judge scoring • Score normalization • Panel discussion • Tie-break by Executive Sponsor • Approval and announcement "
- Assistant
Done! I built an elegant interactive flowchart for the full Hackathon process. Here's what's included:
Design:
- Dark editorial aesthetic with amber/gold accents, glassmorphic cards, and glowing timeline nodes
- Elegant serif (Cormorant Garamond) headings paired with clean sans-serif body text
- Animated scroll-triggered reveal for each section
11 Sections Covered:
- 8-Week Timeline — Theme selection, objectives, budget, problem statements, CoE review, approvals
- Planning Phase — Theme definition and evaluation criteria publishing
- Communication Plan — Staged timeline (T-30 to post-event)
- Registration — MS Forms, team size 4-6, manager approval
- Kickoff — Keynote, rules, mentor introductions
- Development Sprint — Daily office hours, checkpoints, mid-sprint review
- Demo Day — 5-min demo + 3-min Q&A, architecture & business impact
- Judging Criteria — Weighted framework (Innovation 30%, Business Value 25%, etc.)
- Winner Finalization — Scoring, normalization, tie-break, announcement
Every card is expandable/collapsible with smooth animations. The timeline connects all steps with a vertical line and numbered nodes that pulse gently.
Files built:
index.html,src/index.css,src/App.tsx
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.