🔍
RnDAO workspace
/
🪪
IDconnector
/
🧠
DID User Research
/
Brief: IDconnector user research cycle 1

Brief: IDconnector user research cycle 1

 
Context:
RnDAO is exploring building a DID solution to enable more composability between our ventures. Additionally, we might turn this solution into a startup focused on giving application builders a solution for authentication and login of users in their app. This research is about helping us (in)validate our ideas and discover if/how we can sell such a solution. The core goal of the research is to identify the value proposition for customers (devs building apps).
 
Our tool would integrate easily into their app via an SDK/API and allow people to create a user account with any login method (identifier) they prefer e.g. google signing, discord, twitter, etc. and connect other identifiers to the account
Hypotheses of value propositions for end users (remember that our customers are devs, while end user are the ones who use the apps that devs build):
  • cross-app identity: we can offer a seamless experience akin to moving between apps inside Google’s product ecosystem. No need to reconnect your wallet and sign every time, just smooth flow like a composable product ecosystem.
  • can merge accounts if signed first with google and then with twitter i.e. no duplicate accounts that then can’t be resolved
 
Hypotheses of value proposition for customers (devs):
  • Cross-app Identity: reduces user acquisition friction by making signuplongin/account creation seamless
  • No login: reduces friction by making login unnecessary. No need to connect your wallet/email/discord, you automatically get logged in
  • (plus easy to integrate)
 
We’re preparing a grant for this project and we need the research to verify the grant is not misguided and then figuring out which features to prioritise to get market traction beyond RnDAO’s ventures.
Grant: ‣
Research Brief
Target audience: app builders.
 
Key Research questions:
  • what are the key JTBD:
    • big goals in their own words we can speak to: this so we can frame their “dream outcome” in our marketing materials later on
    • the large job in our context is about adding and maintaining a login/auth system for their app. But what are the sub jobs? which features are key? (look into competitors to understand)
    • pain points they have in building applications and specifically with login/auth systems
  • How do they decide for a login/auth system? how and where do they search?
  • When do problems show up with the login system after it's integrated? Who finds those problems, and what impact does it have? What are the most common frustrations with selected tools?
  • what competitors are there, what are they missing? what are they doing right?
 
Nice to haves:
  • ideal target audience: devs or product managers are the ones deciding which system to use? which group can we target more effectively (Go to Market channel, so not just the abstract persona but what group gives better response rate)
 
Timeline:
initial insights within 2 weeks, deeper stuff as we advance.
we want to start having insights as soon as possible as we’re submitting a grant for this.
 
Deliverables:
  • Real time insights: share a TLDR or each conversation as they happen, and share drafts of final report every week
  • Final report with:
    • List of JTBD, ranked for priority
    • A value proposition that works for app developers and managers
🔍
RnDAO workspace
/
🪪
IDconnector
/
🧠
DID User Research
/
Brief: IDconnector user research cycle 1

Brief: IDconnector user research cycle 1

 
Context:
RnDAO is exploring building a DID solution to enable more composability between our ventures. Additionally, we might turn this solution into a startup focused on giving application builders a solution for authentication and login of users in their app. This research is about helping us (in)validate our ideas and discover if/how we can sell such a solution. The core goal of the research is to identify the value proposition for customers (devs building apps).
 
Our tool would integrate easily into their app via an SDK/API and allow people to create a user account with any login method (identifier) they prefer e.g. google signing, discord, twitter, etc. and connect other identifiers to the account
Hypotheses of value propositions for end users (remember that our customers are devs, while end user are the ones who use the apps that devs build):
  • cross-app identity: we can offer a seamless experience akin to moving between apps inside Google’s product ecosystem. No need to reconnect your wallet and sign every time, just smooth flow like a composable product ecosystem.
  • can merge accounts if signed first with google and then with twitter i.e. no duplicate accounts that then can’t be resolved
 
Hypotheses of value proposition for customers (devs):
  • Cross-app Identity: reduces user acquisition friction by making signuplongin/account creation seamless
  • No login: reduces friction by making login unnecessary. No need to connect your wallet/email/discord, you automatically get logged in
  • (plus easy to integrate)
 
We’re preparing a grant for this project and we need the research to verify the grant is not misguided and then figuring out which features to prioritise to get market traction beyond RnDAO’s ventures.
Grant: ‣
Research Brief
Target audience: app builders.
 
Key Research questions:
  • what are the key JTBD:
    • big goals in their own words we can speak to: this so we can frame their “dream outcome” in our marketing materials later on
    • the large job in our context is about adding and maintaining a login/auth system for their app. But what are the sub jobs? which features are key? (look into competitors to understand)
    • pain points they have in building applications and specifically with login/auth systems
  • How do they decide for a login/auth system? how and where do they search?
  • When do problems show up with the login system after it's integrated? Who finds those problems, and what impact does it have? What are the most common frustrations with selected tools?
  • what competitors are there, what are they missing? what are they doing right?
 
Nice to haves:
  • ideal target audience: devs or product managers are the ones deciding which system to use? which group can we target more effectively (Go to Market channel, so not just the abstract persona but what group gives better response rate)
 
Timeline:
initial insights within 2 weeks, deeper stuff as we advance.
we want to start having insights as soon as possible as we’re submitting a grant for this.
 
Deliverables:
  • Real time insights: share a TLDR or each conversation as they happen, and share drafts of final report every week
  • Final report with:
    • List of JTBD, ranked for priority
    • A value proposition that works for app developers and managers