Getting Started with BB: Focus on What, Not How
In our previous post, we explored the power of objective-focused thinking. Now, let's look at how to put this into practice with BB. We'll use the creation of these very blog posts as our running example, showing you exactly how this approach works in real life.
Before You Start
Remember: BB works best when you focus on outcomes rather than implementation details. You don't need to know how BB will accomplish something to ask for what you want.
The Challenge of Thinking in Objectives
Most of us are trained to think in tasks and implementations. It's natural - our education and work experiences often focus on "how" we do things rather than "what" we want to achieve. As one BB user observed:
"Most people think in tasks; it's harder to step back and think about outcomes."
This tendency often comes from tying our self-worth to our abilities - we want to prove we can handle the technical details. But what if we could focus purely on objectives and let BB handle the implementation details?
Starting Your First Conversation
Let's look at how this works in practice. Here's how we started planning these blog posts:
The Traditional Approach:
- Decide on blog post topics
- Research writing techniques
- Create content outlines
- Write draft content
- Edit and revise
The BB Approach:
- State the objective: "I want to add some real blog posts"
- Provide context: "Please read these files..."
- Let BB ask clarifying questions
- Collaborate on planning
- Document decisions for future reference
Notice how the second approach focuses on what we want to achieve rather than how we'll achieve it.
Pro Tip
Start broad with your objectives and let BB's questions guide you to the specifics. This often leads to better solutions than if you had specified all the details upfront.
The Power of Documentation-Driven Conversations
One of the key strategies for success with BB is using documentation to drive conversations. Here's how it works:
Initial Conversation
- State your objective
- Provide context
- Let BB ask questions
- Make decisions
Document the Outcomes
- BB creates structured documentation
- Captures decisions and rationale
- Plans next steps
Follow-up Conversations
- Use documentation as starting point
- Build on previous decisions
- Maintain context and momentum
Common Mistake
Don't try to handle everything in one conversation. Use documentation to break complex objectives into manageable pieces, and let each conversation build on previous progress.
Real Example: Creating These Blog Posts
Let's see how this worked for creating these posts:
Initial Planning Conversation
- Objective: Create engaging blog content
- Context: Shared brand guidelines and ideas
- BB asked about priorities and examples
- Created structured plan
Documentation Creation
- BB documented the plan
- Included post outlines
- Listed real-world examples
- Planned follow-up posts
Follow-up Execution
- Used documentation to guide writing
- Maintained consistent messaging
- Built on established examples
Real Results
This very blog post was created using this approach. The documentation from our planning conversation guided the writing, ensuring we stayed focused on our objectives.
Writing Effective Objectives
The key to success with BB is learning to write effective objectives. Here are some examples:
Less Effective:
"I want to use Swift to create a phone app"
- Focuses on implementation
- Limits possible solutions
- Gets stuck in technical details
More Effective:
"I want an app to help auties"
- Focuses on outcome
- Opens possibilities
- Leads to meaningful discussion
Best Practices for BB Conversations
Start with Context
- Share relevant documentation
- Explain background
- Provide examples
Let BB Guide You
- Answer clarifying questions
- Consider suggestions
- Explore options
Document Everything
- Let BB create structured documentation
- Use it for future conversations
- Build on previous work
Focus on Outcomes
- Think about what you want to achieve
- Stay open to different approaches
- Let BB handle implementation details
Need Practice?
Visit our interactive guide to try converting implementation-focused statements into objective-focused ones.
Common Patterns for Success
The Context Pattern
You: Here are the relevant files... BB: Let me review those and ask questions... You: [Provide answers] BB: Based on this, here's a structured plan...
The Documentation Pattern
BB: Let me document our discussion... [Creates structured markdown] You: [Use this in next conversation] BB: Building on our previous documentation...
The Refinement Pattern
You: Here's my objective... BB: Let me ask some clarifying questions... You: [Provide clarity] BB: Now I understand better, let's explore options...
Your First Conversation
Ready to start? Here's your template:
State Your Objective
- What do you want to achieve?
- Why is it important?
- Who is it for?
Provide Context
- Share relevant files
- Explain background
- Give examples
Engage in Dialogue
- Answer BB's questions
- Consider suggestions
- Explore options
Document and Iterate
- Let BB create documentation
- Use it for follow-up conversations
- Build on your progress
Starting Tip
Begin with a small, well-defined objective for your first conversation. This helps you get comfortable with the process before tackling larger projects.
Remember: Focus on what you want to achieve, not how you think it should be done. Let BB guide you through the process of discovering the best approach to reach your objectives.
Next Steps
Think about an objective you want to achieve. Instead of planning how to do it, try starting a conversation with BB about what you want to accomplish. You might be surprised at the possibilities that open up when you focus on objectives rather than implementation.