Thinking in Objectives
Learn how to maximize BB's capabilities by focusing on what you want to achieve rather than how to achieve it.
The Mindset Shift
BB works best when you think at a higher level of abstraction. Instead of breaking down tasks into step-by-step processes, focus on describing your desired outcomes and let BB handle the implementation details.
Traditional Approach
- Break down tasks into detailed steps
- Research and choose specific tools
- Handle implementation details
- Manage complexity yourself
Objectives Approach
- Focus on desired outcomes
- Describe high-level requirements
- Let BB suggest approaches
- Let BB handle complexity
Key Benefits:
- More creative and comprehensive solutions
- Better focus on business value
- Reduced cognitive load
- Faster implementation
Practice Objective Thinking
Try converting implementation-focused statements into objective-focused ones. This interactive exercise will help you develop the mindset for working with BB effectively.
Practice Objective-Focused Thinking
Convert this implementation-focused statement:
I need to learn a website builder tool
Into an objective-focused statement:
Tips:
- Focus on what you want to achieve
- Think about who benefits
- Consider the broader impact
- Avoid mentioning specific tools or technologies
Real World Examples
Example: App Development
Traditional Approach:
"I want to create a mobile app with these specific features for people with autism..."
✗ Jumps straight to implementation details
Objectives Approach:
"I want to help people with autism better manage daily activities and reduce anxiety..."
✓ Focuses on the core objective
Outcome:
By focusing on objectives, BB could:
- Analyze various solution approaches
- Suggest multiple implementation options
- Guide the chosen solution's development
- Ensure focus remained on user needs
Example: Code Refactoring
Traditional Approach:
"I need to refactor this code to use the repository pattern and dependency injection..."
✗ Focuses on specific implementation patterns
Objectives Approach:
"I want to make this code more maintainable and easier to test..."
✓ Focuses on desired improvements
Outcome:
BB can suggest the best approach based on:
- Current code structure
- Project constraints
- Best practices
- Maintenance requirements
Best Practices
Describing Objectives
When sharing objectives with BB:
- Focus on the "what" and "why" rather than the "how"
- Include context and constraints
- Describe desired outcomes
- Share relevant background information
Working with BB
To get the best results:
- Start with high-level objectives
- Let BB suggest approaches
- Ask questions about suggestions
- Refine based on BB's feedback
Managing Conversations
For complex objectives:
- Break down into smaller objectives
- Use separate conversations for different aspects
- Document decisions and progress
- Review and refine objectives as needed
Common Pitfalls
What to Avoid
- Being too specific: Dictating implementation details limits BB's ability to suggest better approaches
- Skipping context: Not providing enough background information can lead to suboptimal solutions
- Mixing objectives: Trying to handle too many different objectives in one conversation
- Ignoring feedback: Not considering BB's suggestions or alternative approaches
Instead, Try This
- Share outcomes: Describe what you want to achieve and why
- Provide context: Include relevant background and constraints
- Focus conversations: Use separate conversations for different objectives
- Engage in dialogue: Discuss and refine approaches with BB