Behavior Driven Design is suppose to get the developer to think about the overall design better than Test Driven Development (TDD). In reality, it depends on the how well the user story is written. I happen to like the format of (from dannorth.net):

Title

Narrative:
As a [Role]
I want [Feature]
So that [Benefit]

Acceptance Criteria: (presented as Scenarios)
Scenario 1: Title
Given [context]
  And [some more context]...
When  [event]
Then  [outcome]
  And [another outcome]...

Scenario 2: ...

Recently, I have seen some blog post showing their BDD story cards:

As a user
I want to be able to see ...
So that I have ...

They were all IMO missing big point, the role,  USER is not a detailed enough role.  A better example would be:

As a player
I want to be able to see the next scheduled game for my team(s)
So that I can indicate if I can make the game(s)

So really think about the role of the user of the system for the story card, it will make you tests better in the end.