# 9/6/2023 - SmartInvoice 09/23

## Props/Liked
What did we do in the last period that you liked? This includes things you want to acknowledge as well as things you want to make sure we continue to do and build on.
* Seeking out other use cases that can build on the protocol (+5)
* Props to Plor on the new dao structure and comp model (+3)
* Began work on issues that have been stagnant for quite a while (+2)
* We were willing to experiment with new ideas by trying NAVH (+2)
* Gitcoin was generally positive, something to continue building on (+2)
* SmartGrants idea didn't get shot down immediately (thanks!) (+2)
* Incorporated estimation process to standardize pricing per issue (+1)
* Good development initiative with the hackathon (+1)
* We begun to look more outwards and try to find our place in the space. (+1)
* I think SmartGrants is a really cool ideation of SmartInvoice, we should continue pursuing it. (+1)
* Props to Plor to being the trusted and helpful conductor; (+1)
* Liked that ppl are sticking to process. (+1)
* Props to benedictvs for bringing back some life to our twitter handle (+1)
* Props to everyone for being awesome (+1)
* It is nice having more people and energy on the project (+1)
* props@richa: good to add different skillset & perspectives (+1)
* Filled out the product/marketing side to add more momentum beyond development
* We started including contributors with different skillsets.
* Plor put a lot of effort into accommodating everyone in the process.
* Working and chatting with Georgeh is really enjoyable.
* Plor props pt2: Meetings, notes, quick to respond, helping with on-chain actions
* Props to ppl that have in their hearts what is best for the protocol (and not just their personal interest)
* Props to ppl doing their best
* Newer contributors took on initiative with some tasks
* Props to 0xmaker for fixing frontend bugs
* Georgeh and Tufnel stepped up to get polygon ready for E2T (almost got there)
* People seem to have a positive view on our direction
* Lots of process changes seem to be handled gracefully
* Putting up with me is not easy, I also appreciate that.
* Hackthon was fun even though it didn't pan out
* constructive meetings with plentiful sharing of views/ideas
* props@plor: good jestering
* props@benedictvs: slide deck was v. useful in presenting S/I to the Swiss Crypto Valley Assoc. Start-up Working Group
* props@georgeh: cool library for the hackathon

## Issues/Concerns
Where do you find issues in our process? What did not go well that would be useful to change going forward?
* Too many incomplete tasks coming out of sprints. (+4)
* audits, security of user funds needs to be most important, high risk threat (+4)
* not data driven: measuring user engagement, # of visits, # of invoices deployed (+3)
* NAVH: too much left to do at the end (+2)
* Roadmap target of 1000 Invoices: aggressive enough? Should we 10x/100x it? (+2)
* Sprint meetings can become more contentious than I'd prefer. (+2)
* Estimation doesn't seem like a smooth process, needs some work (+1)
* Compensation and budget and runway seems to be unresolved still. (+1)
* RaidGuild association / separation is not fully clear yet. (+1)
* social media/content has room for improvement, tighten up feedback loop, engagement with public/users (+1)
* Our Kanban board is highly developer centric. While I understand why that is, adaptability of processes is a feature not a bug. (+1)
* More of a comment on DAOs in general, but more ownership of work streams and issues beyond individual tasks would assist momentum
* Slow to finish some tasks (than expected)
* Bringing on new contributors hasn't been without pain in onboarding to stack
* We need to separate the protocol decisions from product/workflow decisions.
* Touch points with some team members outside of our weekly meeting is desirable.
* We should try to become more nuanced in our judgements and do not subject every decision to a binary matrix.
* How are we planning to make the most of our runway?
* Do we have a strategy for extending our runway?

## Social Goals
What is your understanding of the goals we had for social media? Also include comments on whether you think they were appropriate goals.
* Engaging in conversations with crypto community, to get feedback on product and signal that we are active and care (+3)
* I believed the original goal was to just show engagement and activity, indicating SI is alive. (That met my baseline expectation) (+3)
* Target audience: potential partners/integrators (+2)
* Get the general word out. Lay the groundwork for engagement when larger future releases (+1)
* Education on how SI works, how we work as a DAO (+1)
* develop trust and relationship with users; (+1)
* Target audience: potential users in emerging markets (non-English also?) (+1)
* Goal was to get a digital footprint so we have more credibility. (+1)
* We don't need viral tweets/blogs, but the right people seeing it is key (+1)
* Educational content to get people to understand the value proposition better than we've explained it to date. (+1)
* Maybe we more towards more governance discussions as we have them and how we can fit into accountability for DAOs (+1)
* Finding out who we are and who we want/ how we want to represent ourselves. (+1)
* Target audience: potential investors
* Goal should be more towards making connections, engage orgs that might want to use SI.
* Getting started and build a presence at all.
* We wanted to surface contentions, conflicts, and friction.
* Experimenting and exploring the network/ bubble we are in.
* You cannot put a face on software, but we should have an evangelist.
* guild.xyz is a prime example where the protocol itself is subtle, but has a vocal advocate with a voice and face.
* We did not want to do growth marketing but content marketing.
* We need to grow our follower base because otherwise (non-)engagement just tells the same story.
* Unclear what the actual goals are now. Bare minimum expectation for me is to announce updates and engage with questions/feedback from users

## Process on Social
What recommendations or comments do you have on the process of social media management?
* more memes? (+4)
* Track more data on tweet & blog views, likes, comments. Look at this data at start of every meeting. (+2)
* Having a team that is creative and diverse would help the ideation process (+2)
* maybe we should have a monthly budget rather than estimate it like bugs (+1)
* Delineate responsibility: who's responding to inbound queries? (+1)
* Metrics? (+1)
* Enable article / twitter posting for all SI team that care to. Have discussion on how to do compensation. (+1)
* Suggestion: Have weekly budget on SM, split between all contributors. (+1)
* Discord bot to notify us of newly posted tweets (+1)
* It is difficult to get developers to share their insights while following the lead. (+1)
* Set a vision that most contributors buy into and develop a strategy that is longterm (+1)
* A content plan is already rigid. We need to figure out how to connect this to the development.
* Connect it to IRL and personal outreach.

## Action points
* Make sure we lean into many different use cases. Particularly with privacy.;
* Add achievable goals that are big enough to force us outside the box. ;
* Get metrics for site and social. Discuss at start of meetings.;
* Make proposal for social budget.;