Module 6: Recipe and Development Workflow
This module focuses on the connection between HubSpot and recipe/development activity. It helps learners understand how the process moves from tracker-based management into development work and back again.
Why This Module Matters
The process depends on development activity being connected to system visibility. If recipe work happens outside the tracker without clear links back, the wider team loses control and transparency.
Learning Objective
By the end of this module, learners will understand how recipe development fits into the HubSpot workflow and how users navigate between the system and development activity.
Videos Included
Lesson 6.1
How Recipe Work Fits Into the Process
Lesson purpose
This lesson explains where recipe and development work sit in the broader customer project flow.
What learners should understand
Recipe creation is not separate from HubSpot. It is part of the wider workflow and should support progression, visibility, and handoffs.
Key points
- development work is part of the tracked process
- recipe activity supports sample and progression stages
- system visibility should not be lost when work moves into development
What good looks like
- the learner understands how development supports the overall workflow
- the learner can explain why recipe work still needs process discipline
Common mistakes
- treating development work as disconnected from HubSpot
- focusing only on the technical work and not on tracker visibility
Quick check
Ask the learner to explain how recipe activity connects back to the live project workflow.
Lesson 6.2
Navigating to Recipe Creation
Lesson purpose
This lesson teaches learners how the system links them into recipe creation activity.
What learners should understand
The handoff from HubSpot to recipe work should be clear and easy to follow so that users can move between operational tracking and development work without losing context.
Key points
- navigation should be simple and repeatable
- users should understand where they are going and why
- the connection between systems should feel controlled, not ad hoc
What good looks like
- the learner can describe the navigation path
- the learner understands how the development workspace connects to the project
Common mistakes
- losing context when leaving HubSpot
- not checking that the correct project or product is being worked on
Quick check
Ask the learner to explain what they would check before starting recipe work from a HubSpot-linked record.
Lesson 6.3
Maintaining Process Visibility During Development
Lesson purpose
This lesson focuses on keeping the wider process visible while work is happening in development.
What learners should understand
Even when work is happening in recipe development, the rest of the business still needs visibility into where the project sits and what is likely to happen next.
Key points
- development work should still support tracker updates
- visibility supports handoffs and planning
- operational tracking and technical work must stay aligned
What good looks like
- the learner understands that development activity should not create a visibility gap
- the learner can explain why alignment matters
Common mistakes
- allowing the tracker to become outdated while work continues elsewhere
- assuming visibility can be updated later without impact
Module 6 Key Takeaways
- recipe work is part of the same controlled process
- HubSpot and development activity should stay connected
- visibility during development is essential for the wider team
Module 6 Suggested Assessment
Ask the learner to:
- explain where recipe work fits into the full workflow
- describe how they would move from HubSpot into recipe work
- explain how the process stays visible while development is happening