# data[].attributes.headline
Any immediate next steps for the company coming out of this project/debrief?

# data[].attributes.subject
Any immediate next steps for the company coming out of this project/debrief?

# data[].attributes.headline
What about this project REINFORCED our current knowledge, approach, and practices?

# data[].attributes.subject
What about this project REINFORCED our current knowledge, approach, and practices?

# data[].attributes.body
Where did our processes and approach work well?

What made you think "we should continue doing X this way"?

# data[].attributes.body
(As well as any other OL content coming out of this discussion)

# data[].attributes.attachment_link.description
You’ll need to enable cookies in your browser for Basecamp to work properly.

# data[].attributes.headline
What about this project CHALLENGED our status quo?

# data[].attributes.subject
What about this project CHALLENGED our status quo?

# data[].attributes.body
Did anything about this project make you less certain about something you previously thought?

What surprised you?

What made you think "maybe we should consider changing how we do X"?

# data[].attributes.headline
What questions did this project spark for you?

# data[].attributes.subject
What questions did this project spark for you?

# data[].attributes.body
(Also anything we should add to our Thorny Questions List? https://3.basecamp.com/3538194/buckets/2532526/messages/7753073995"

# data[].attributes.attachment_link.description
You’ll need to enable cookies in your browser for Basecamp to work properly.

# data[].attributes.headline
How did we work together? (planning, decision-making, etc.)

# data[].attributes.subject
How did we work together? (planning, decision-making, etc.)

# data[].attributes.headline
Worked Well: Interesting content and the client really cared about it

# data[].attributes.subject
Worked Well: Interesting content and the client really cared about it

# data[].attributes.body
It was clear that Nate really cared about the project going well and being useful, same with all of the other CV teams we spoke with.

# data[].attributes.body
This wasn't our usually team set up (there was no associate) but I thought it worked well and allowed all of us to stretch out legs a bit. I loved how creative Eliel was able to be with deliverables and how we could be flexible when it came to tasks.

# data[].attributes.headline
Worked Well: Client seemed very satisfied by our work

# data[].attributes.subject
Worked Well: Client seemed very satisfied by our work

# data[].attributes.body
Nate seemed really happy with the finished products, as did the core team and executive team. I noticed they were especially happy with the spheres of influence model, the interview protocol/best practices, and the client interview summary.

# data[].attributes.headline
Client seemed satisfied with products  across the e-team, core team etc

# data[].attributes.subject
Client seemed satisfied with products  across the e-team, core team etc

# data[].attributes.headline
Worked well: Client building relationships with partners

# data[].attributes.subject
Worked well: Client building relationships with partners

# data[].attributes.body
Nate did a good job at building relationships and trust, which made our role in workshops smoother

# data[].attributes.body
Client knew what they wanted and were really clear with their communication

# data[].attributes.headline
Our client contact was really busy at times which paused challenges for scheduling and feedback. 

# data[].attributes.subject
Our client contact was really busy at times which paused challenges for scheduling and feedback. 

# data[].attributes.headline
Could be improved: Client communication and buy in

# data[].attributes.subject
Could be improved: Client communication and buy in

# data[].attributes.body
Sometimes it was really difficult to get responses from the client outside of meetings. In meetings, they had a ton to say and a lot of amazing thoughts, but didn't provide much outside of meetings. And it was sometimes difficult to schedule meetings. It also felt like, in our last meeting with the E-Team, there were some struggles with implementation and buy-in.

# data[].attributes.body
It was a small project and we ended up adding a deliverable (interview summary).

# data[].attributes.body
Small team allowed us to be flexible in figuring out tasks and todos between us

# data[].attributes.headline
Learned: I learned a lot about federal regulations

# data[].attributes.subject
Learned: I learned a lot about federal regulations

# data[].attributes.body
Which I love.

# data[].attributes.body
Thought we worked really well as a team tag teaming tasks and responsibilities. We didn't have an associate for this project which meant that Emily had to play both roles sometimes. For the size of the project it worked really well but if this project was any larger budgeting more time for an RA that plays both roles would be important.

# data[].attributes.body
CDFIs were new to our team. We learned that there is a whole new space/area that has the potential to include evaluation but may not be called evaluation. Potential for new stands of work and field.

# data[].attributes.headline
Could be improved: Reasonable scope/improving efficiency

# data[].attributes.subject
Could be improved: Reasonable scope/improving efficiency

# data[].attributes.body
Might not be able to improved with a bigger budget, but making sure we discuss what is feasible with a given budget

# data[].attributes.body
Full budget was around $50k

# data[].attributes.body
Very difficult. Lots of follow-ups and back and forth